Skip to content
العربيةLet’s talk

Practical guide

How to test a website enquiry from the form to the right Odoo CRM team

Submit an Arabic and an English enquiry, find each record in Odoo CRM and check that the right salesperson can read the request and send the first reply.

Lava Solutions · · 3 minute read

Two people arrange sticky notes on a glass board during a planning workshop.
Illustrative stock photo. Photo: airfocus / Unsplash.

Take the seat of the salesperson who opens tomorrow morning’s enquiries. Can they find a request from the website, read exactly what the visitor asked and reply to the right address? A useful acceptance test starts on a public-facing form and ends when a reply reaches a test inbox. Give the website editor and the sales supervisor different parts to play so that a routing problem is visible to both.

Write down where each enquiry should land

Choose one real entry point, such as the “Request a quote” form. List its English and Arabic page addresses, the team that covers it, who checks unassigned enquiries, and where a visitor should receive the first reply. Decide whether this form should create a lead for qualification or an opportunity ready for follow-up. Ask the sales supervisor to write down the expected result before opening the editor.

For an Odoo Website form connected to CRM, inspect the form action. Odoo 19 documents email as the default action. To capture the enquiry in CRM, choose Create an Opportunity and select the sales team. If the CRM Leads setting is on, that action creates a lead. If a salesperson is selected on the form, check that person’s queue. If the field is empty, inspect the team’s assignment rules and who handles a record while it awaits assignment.

Follow two labelled enquiries into CRM

Fictional example. An equipment distributor wants quote requests in both languages to reach its Projects team. The team qualifies leads before creating opportunities. In a test environment, give each submission a different subject and use addresses that your testers control. Keep the same requested quantity so that differences in handling are easy to spot.

  1. From the Arabic page, submit a request for twelve shelving units with the reference AR-12 in the subject. From the English page, request the same items using EN-12. Record the page, time and acknowledgement for each.
  2. Have the supervisor search for each reference in the expected CRM view. Record the record ID, type, team, assigned person, reply address and full message. Read the Arabic text back and check the quantity and line breaks if they affect the request.
  3. Sign in as the person who normally handles that queue. Ask them to open the record and send a short reply to the test address through the usual workflow. Have the tester confirm which inbox received it and which reference appeared in the reply.

Use the result to locate the fault

If the form shows a success message but the team sees nothing, check the form action and whether the database created a lead. Then search with an authorised supervisor account and remove any personal pipeline filter. A record found under the wrong team points to routing. A record visible to a supervisor alone calls for a closer look at assignment or salesperson access. A record with the right owner but no question points to field mapping. Inspect the saved record before making another change.

For a website built elsewhere, identify which form actually processes the submission. Odoo documents embedding a form hosted on Odoo Website inside another site. If your developer chose a connector for a separate form instead, run both tests through that connector and have the developer trace one reference across the handoff.

Agree who takes the first reply after launch

Keep the two page addresses and CRM record IDs alongside the expected team, reply evidence and the name of the person covering unassigned requests. Repeat the test after changing a form or its destination. For what happens after qualification, see the Odoo CRM stage review. To scope the website handoff with Lava, send the two page addresses and the intended sales team.

Sources & further reading

A useful next step

Bring one real workflow.

Share the process you want to improve, the systems involved and the decision you need to make.

Talk to Lava ↗