When an export website receives an enquiry, use the buyer's project country or region and product family to choose one sales owner. Specify who provides technical help and who takes over unclaimed enquiries. Each enquiry should have a traceable submission number, an owner and a first contact time. A shared assignment sheet and a duty coordinator work well when volume is low and rules change often. Consider automated routing when regional sites already share a CRM, the rules are stable and manual handoffs regularly get missed.
This guide is for teams serving multiple markets or product lines, or operating several regional websites. Use the routing matrix, exception order, handoff deadlines and test records in your website brief and acceptance checks.
1. Align routing fields across languages
- Project country or region: Ask where the equipment will be installed or where the project will be delivered. Offer an “Undecided” option. Browser language, domain and IP can help diagnose an issue. For instance, when a German headquarters requests a quote in English for a Brazilian plant, the regional rule uses Brazil.
- Product: Keep a stable product family ID and collect a model number where useful. Translate the labels in the form, and submit the same family ID in both languages. For a shared catalogue, first check the mapping between product IDs and site records.
- Request type and contact details: Distinguish quotes, support, partnerships and other requests, and ask for one usable contact channel. Buyers who are unsure about the product can describe their needs so the coordinator can fill in the details later. Make reply language optional.
- Source: Keep the site, form, page and submission time for troubleshooting. Validate any product ID supplied by the theme against the site and its available products on the server. Hidden fields sent by the browser can also be altered.
2. Put region and product rules in priority order
Start with who owns the next step with the customer. Regional sales usually handles quotes, time zones and channel handoffs. Product specialists help with specifications and solutions. A product line with its own sales team can have an explicit exception. Have the sales lead approve rule priority, effective dates, primary owners and backups.
- Apply business exceptions first: Send support requests to the service coordinator, for example. An existing customer can stay with their account owner once reliable records confirm the match and the owner is available and authorised for the project territory. Send conflicts to the duty coordinator for review.
- Match region and product: Apply an approved rule for the combination first. When only the region is known, the regional coordinator can clarify the product. Record the matching rule ID. Resolve any tie between two primary owners at the same priority before enabling the rules.
- Catch unmatched requests: Route unknown regions, invalid products, cases spanning regions or ownership disputes to a staffed queue. Have its coordinator clarify and assign the enquiry, recording the reason.
For examples of routing choices, see Made-in-China's consultation routing guide (Chinese) on countries, products and exceptions, and Salesforce's lead planning guide on territories, product interest and queues. Set the rule order around your own sales responsibilities.
3. Fictional example: a German buyer requests a quote for Brazil
The regions, product code, rules and deadlines below are illustrative. Suppose an English product page enquiry comes from a German headquarters for a Brazilian project: family PX, request type quote, preferred reply language English. Rule R2 assigns it to Latin America sales, with a PX engineer helping on specifications. If the buyer selects “Undecided” for the project location, the same form follows R3. The coordinator confirms the project location and hands off the enquiry.
| Rule | Condition | Primary owner |
|---|---|---|
| R1 | Support request | Service desk |
| R2 | Brazil project, PX quote | Latin America sales |
| R3 | Region undecided or no match | Duty coordinator |
Example service targets: claim the enquiry within two business hours and make the first human contact within one business day. Use the agreed time zone and business calendar for evenings and holidays. If a deadline slips, the duty manager contacts the backup. Record the former and new owner, time and reason for each reassignment. Track notification, claiming and customer contact as separate events.
4. Choose manual triage or CRM routing
Manual triage: Save enquiries through CatchCMS forms and review submissions by site and form in the admin. Set fixed notification recipients for each form if needed. Give one coordinator the assignment sheet and use a shared tracker with restricted access for ownership and deadlines. Split forms when an entry point has a lasting difference in purpose, fields or ownership. A shared entry point reduces repeated maintenance across sites. Verify the saved submission first, then check delivery separately with the enquiry form and email troubleshooting guide.
CRM routing: Consider integration when you already have shared sales queues and need assignment across sites, handoffs or reminders. CatchCMS provides custom forms, submissions scoped to each site, processing status and email recipients configured per form. Routing by field values, CRM sync, ownership tracking, retries and overdue escalation require project configuration and integration work. Prefilling a product from the theme also needs implementation and testing. Include each requirement in the quote using the export website feature checklist.
5. Plan for manual recovery when CRM delivery fails
Track four checkpoints: saved on the website, received by the CRM, claimed by the owner and first customer contact. Use a fixed source identifier plus the submission number as a unique key for delivery. Enforce key uniqueness and write by key in the CRM. Where the CRM lacks that capability, process one delivery at a time for each key and hold any delivery with an uncertain outcome for reconciliation. Look up or reuse the same CRM record on each retry. A later enquiry from the same buyer has a new submission number and can be linked to the existing customer while retaining the new request. Keep the site, form, rule version and CRM record ID for reconciliation across sites. Limit the everyday assignment tracker to information people need to follow up, and restrict access to the original submission.
A request can time out after the CRM has saved it. Look up the delivery key at the destination. Retry once you confirm that the first request has finished and created no record. If the outcome is unclear, have the coordinator and system owner reconcile it. Put confirmed failures on an exception list so the coordinator can take over from the original submission. When creating a record manually, save the same key and record the handoff, then reconcile before any subsequent retry. Compare website submissions against CRM receipts and exceptions each day so each pending enquiry has an owner and a next action.
6. Acceptance checks: send six labelled test enquiries
- Submit the same region and product on the Chinese and English pages. Both independent submissions should match the same rule and store identical routing values. Their source pages and languages should remain traceable.
- Submit a PX quote for a Brazilian project from a German headquarters. Verify the Brazil rule and confirm who handles sales and technical questions.
- Submit an undecided region or a request without an available product. Verify that the coordinator can pick it up, complete the record and reassign it.
- Submit a support request or use an existing test customer to trigger an agreed exception. Verify priority and one primary owner.
- Submit one enquiry to simulate integration failure. Verify that the website saves it and the failed delivery is recorded. Replay the same submission number in the test environment and verify that it ends up with one CRM record.
The first check uses two submissions, for six in total. Use an isolated test site and dedicated inbox, and submit at least one on a phone. Record test ID, site and page, submission number, rule and version, owner and backup, claim and first contact times, and sync or manual recovery result. Check visibility using test accounts for the real roles, then have the sales lead sign off on the rules and duty schedule.
7. Frequently asked questions
Should every enquiry from the English site go to a sales rep who speaks English?
Choose the sales owner by confirmed project location and product. Use the buyer's preferred language to arrange a reply. Refer disputes over territories or sales channels to the coordinator under the exception rules.
Does notifying two people help prevent missed enquiries?
Notifications can keep collaborators informed. Assign one primary owner and one backup, and record claiming and first human contact. A shared queue also needs an identified coordinator on duty.
What should we bring to the website project?
Prepare a list of regions and product families, primary and backup owners, two common exceptions, an anonymised sample enquiry and details of existing CRM fields and integration options. Share the site, language and handoff requirements through CatchCMS project consultation. Start by testing the full path from form submission to sales claiming for one region and one product family.