A customer reaches a business group through its parent website, but the right person to handle the work may sit in a specialist company. That is common with a portfolio covering engineering, project advisory, branding, IT, search marketing and technical services. A referral can save the customer time. It can also create confusion about who received their information, which company is responsible for a quote, and what happens next.
The safest process is not to copy every enquiry to every company. It is to identify the service needed, explain the destination to the customer, transfer only the information needed for an agreed purpose, and keep ownership visible. This guide gives business owners and teams a practical process for doing that. It is general operational guidance, not legal advice or a statement about any particular company’s internal systems.
First, help the visitor understand which specialist handles which kind of work. A parent-company site should describe the relationship between businesses and link to the right specialist’s own service pages. It should not imply that the parent supplies every service directly, especially where technical qualifications, project scope or commercial terms belong with the operating business.
For example, someone looking for a custom printed part may need a printing specialist, while a person planning a website migration needs IT support. The parent website can make the distinction clear through its company directory and approach to specialist handoffs. A clear destination reduces wrong enquiries before any personal information is handled.
A link is not the same as an internal referral. When a visitor clicks through and contacts the specialist directly, that specialist can collect the information needed for its own work. When the parent receives personal details and proposes sending them elsewhere, the team should determine what can be shared and on what basis.
An enquiry might contain a name, email address, phone number, project drawings, photographs or commercially confidential information. Some submissions may include information the customer did not need to provide. Before forwarding anything, record the original purpose of collection, the proposed recipient and the reason each item is needed.
Australia’s Office of the Australian Information Commissioner explains that Australian Privacy Principle 6 regulates the use or disclosure of personal information by entities covered by the Australian Privacy Principles. Secondary use or disclosure generally requires an applicable basis, such as valid consent or a related purpose the individual would reasonably expect. Related companies should not simply assume that an enquiry can be circulated across the group. The precise legal position depends on the entities, information, context and applicable laws.
Use a simple decision note: What was requested? Who should handle it? What information is necessary? What notice or permission applies? If those answers are unclear, ask the customer to contact the appropriate business directly instead of forwarding the whole submission.
A good handoff message answers four practical questions. Which business will respond? Why is that business a better fit? What information will be passed on? When and how should the customer expect contact? Avoid a vague statement such as ‘we have sent this to our team’ when the recipient is a separate operating company.
For an enquiry that needs a human referral, a simple message could say: ‘Your request appears to relate to a specific service. With your agreement, we can introduce you to the specialist business and share your contact details and short project summary. Alternatively, you can contact them directly.’ Adapt the wording to the actual process and privacy notices. Do not make promises about response time unless the receiving company has agreed to them.
If a customer has already provided attachments, check whether each file is needed. A short technical summary may be enough for the first contact. The receiving specialist can request detailed drawings or specifications through its own secure process once scope is established.
Referrals fail when everyone assumes someone else will act. Assign one person or team to accept the referral and record the handoff date. A useful minimum register includes the enquiry reference, origin, destination company, service category, permission or legal basis recorded where relevant, sent date, recipient, and acceptance status. Avoid storing unnecessary personal details in that register.
Acceptance matters more than merely sending an email. A referral should become ‘accepted’ only when the receiving party confirms responsibility. If an enquiry is outside the specialist’s scope, it should return to the original contact for a clear answer rather than disappear into an inbox. This is an operating practice, not an indication that a particular company has implemented a group-wide system.
To reduce coordination gaps, distinguish referral owner, delivery owner, and commercial owner. The referral owner helps the customer reach the specialist. The delivery owner assesses technical suitability. The commercial owner prepares any quote and terms. Those roles may be held by the same person in a small business, but the responsibilities should still be clear.
Start with the smallest useful dataset: a contact method and a brief description of the requested service. Do not attach unrelated previous correspondence, customer lists, credentials or full project folders merely because they happen to be in the original conversation. Confirm the recipient address or portal before sending. Where information is sensitive or confidential, use an approved secure transfer method rather than a long forwarded email chain.
Business.gov.au’s guidance on protecting customers’ information is a useful starting point for understanding how businesses can handle customer data responsibly. Check what legal obligations apply to your business rather than assuming that all organisations have identical requirements. Also consider who can access shared inboxes and whether former staff and vendors retain access after their work ends.
These steps connect with a broader ownership map for shared digital suppliers: who controls mailboxes, forms, websites, shared drives and integration accounts? A referral process is only as reliable as the systems that transmit and store it.
A customer who wants a quote for one service has not necessarily requested marketing from every business in a portfolio. Treat service fulfilment, cross-referrals and promotional campaigns as different purposes. Review the applicable privacy obligations, consent records and unsubscribe mechanisms before using enquiry information for another company’s marketing list.
A helpful customer experience does not require an aggressive cross-sell. Where a second service genuinely supports the first, explain the relationship and let the customer choose whether to start a separate conversation. This also helps the businesses measure which enquiries were relevant rather than treating every group contact as a lead for everyone.
Consider three example enquiries. A person asks the parent company for a one-off 3D printed replacement part. The parent points visitors to the 3D Print Brisbane group profile and the specialist website, explains that design suitability and quoting sit with that business, and does not forward unrelated information. A business owner asks for a new website and ongoing SEO. The initial recipient clarifies whether the requirement covers two specialties, then identifies who will coordinate the brief and which company will quote each part. An engineering client submits drawings. Before any referral, the team checks confidentiality obligations and the appropriate recipient; an unsolicited broadcast of the drawings would be inappropriate.
Test the workflow from both ends. Can the customer find the right business on a phone? Does the form explain who receives the information? Does the receiving company confirm acceptance? Is there a route for mistakenly assigned enquiries? Are stale referrals escalated? A brief monthly sample of anonymised cases may reveal more than publishing another generic service page.
Before marking an enquiry as handed over, confirm that the destination business matches the requested service; the customer knows which business will respond; the information shared is necessary and permitted; the receiving person has accepted responsibility; any technical files use the right channel; quotation and delivery responsibilities are clear; and the original contact knows how to follow up if no response arrives.
Where the enquiry is incomplete, use a clear specialist enquiry brief to obtain the missing scope without collecting more personal data than needed. The checklist is a quality tool: it should make transfers more reliable, not become a reason to delay a straightforward request.
A parent-company site should measure whether people reach the correct specialist, not just how many visits its articles receive. Useful indicators include the share of enquiries directed to the correct company first time, accepted referrals, referrals returned as out of scope, response time from acceptance, and cases where the customer needed to repeat information. Track these in aggregate and avoid unnecessary personal data in analytics.
When reviewing performance, separate brand searches for the parent from searches for each specialist. One parent-company article should not compete with a subsidiary’s service page for a technical sales query. Internal links can help visitors reach the best destination, while accurate page titles and descriptions explain the relationship before the click.
The most useful role of a parent-company website is to make a varied portfolio easier to navigate. Clear service boundaries, careful data handling and an explicit next owner make that promise practical. They also help each specialist focus on enquiries that match its expertise.
For an overview of the specialist businesses, visit XGEN Group companies. For parent-company enquiries, use the XGEN Group contact page. Service-specific enquiries are best directed to the relevant operating business.
Sources and further reading: OAIC: APP 6, use or disclosure; Business.gov.au: protect customers’ information; Google Search Central: people-first content.