Skip to main content

Workflow solutions / CraftDuka

Website enquiry routing to an accountable salesperson

Route a validated website enquiry to the right salesperson using service interest and assignment rules. Preserve the submission before trying downstream notifications.

Who this suits

Sales teams whose website submissions reach a shared inbox without clear ownership.

When a simpler option is a better fit

If one person handles all enquiries reliably, a monitored inbox may be enough without a separate routing engine.

Proposed workflow

  1. Validate contact fields and service interest

  2. Match an existing contact and apply the assignment rule

  3. Create a follow-up task and confirm the responsible owner

Illustrative operating rules

Form-to-owner journey, required fields, routing rules, and duplicate handling

Illustrative design example. Adapt these rules with the responsible team before implementation.

Website enquiry routing to an accountable salesperson: decisions and ownership
Record or decisionIllustrative ruleAccountable owner
Service interestRoute business systems enquiries to the designated specialistSales coordinator
Existing customerRetain the account owner unless reassignment is approvedAccount manager
No matching ruleAssign the fallback queue rather than discard the requestSales lead

Required inputs

  • Form schema and spam controls
  • CRM access and assignment roster
  • Submission identifiers and a monitored fallback queue

Limits and exceptions

Use a submission ID to prevent duplicate tasks. An ambiguous contact match should go to review; a CRM outage must leave the saved submission available for recovery.

Scope and operating costs

Costs depend on form sources, routing branches and CRM fields. Begin with one validated form and a small set of assignment rules.

Acceptance and measurement

Measure unassigned enquiries, duplicate tasks and time to an owned next action. A notification sent without an owner is not completion.

Questions before starting

What inputs does this workflow need?

Form schema and spam controls; CRM access and assignment roster; Submission identifiers and a monitored fallback queue.

Discuss the scope and availability

Tell CraftDuka about the task, your current systems and the people who will use it. Our team is based in Nairobi and serves Kenya and East Africa. We will assess the fit and availability before agreeing a project.

Privacy policy