Independent case / interactive lab

B2B enquiry qualification and contact review

Synthetic equipment enquiries distinguish a new contact, an existing contact with a new request, a repeat event and a general question.

CRM lead routing lab

Browser-local rules · inspectable inputs

Loading the demonstration…

Execution & evidence

What this case establishes.

The manual workflow ran in n8n and returned eight passing acceptance checks. Its record store is an in-execution demo object. The deliberate destination failure is a fixture, not a failed live API.

Actual n8n execution with verified output and eight passing acceptance checks
Scope and limitations
  • Test enquiries are synthetic and contain no real customer contact details.
  • A demo record store is distinguished from a live CRM connection.
  • External replies and production record changes require a defined approval path.
Acceptance checks
  • Recognize a repeat event without creating another opportunity.
  • Keep a general enquiry as a contact-only update.
  • Show the reason and missing information behind each route.

Technical references

References inform the design. They do not imply a connected account or an endorsement.

A bounded first engagement

Start with one clear outcome.

One channel, one CRM data model and a signed-off routing matrix. Channels, custom fields, languages and real reply behaviour are separate scope decisions.

Discuss on Upwork