Home

Structuring a group website so customers find the right business unit

An organisation chart explains ownership. Customers usually arrive with a product, location or service in mind. Give them a route from that need to the responsible unit and its enquiry channel.

Responsible unit

Test a realistic task: find the unit serving a specific region and send an enquiry to its team. Identify where group-level information ends, who owns the local page and where an enquiry goes when several units share a service.

Visitor need → Responsible unit → Enquiry route
Visitor need → Responsible unit → Enquiry route

Does a regional enquiry reach the responsible unit?

When two subsidiaries cover the same product, let the visitor choose a location or application rather than asking them to recognise legal company names. Check that both paths reach the intended local team.

Illustrative record: Visitor selects region (REGION B) / Receiving business unit (TEAM B ?)
Test neighbouring regions as separate cases. If both arrive at headquarters, record whether central triage is intentional and who forwards the enquiry to the local team.

Acceptance evidence · Receiving business unit

Simulate renaming a subsidiary. Count the menus, pages, documents and language versions that must change. Store shared identity and contact routing in an owned reference so that an organisational change does not leave conflicting information online.

Review one service-finding journey and your business-unit list with DigiWeb

Let’s start with
what you need.

Tell us about your project or the website issue you need to resolve. DigiWeb will work through the next steps with you.

info@digiweb.com.vn0902 604 802Nguyễn Đức Thái · Founder DigiWeb