assess.one – AI-powered business operations platform

Workflow Template

Product Enquiry Contact Form Workflow

A lightweight workflow for a public website product enquiry form. Captures name, email, optional phone, product of interest and message; creates a record; sends immediate confirmation (email + SMS if mobile provided); classifies and prioritises the enquiry; assigns it to the right sales/product contact; captures the response; closes the enquiry with a closure email; and sends an optional feedback request 1 day after closure.

Organisations that rely on public-facing product enquiry forms need a governed, traceable process for handling customer contact data, from initial capture through to response and closure, particularly where response-time expectations or data handling obligations apply. This workflow spans marketing, sales, and product teams, providing a structured record of each enquiry's lifecycle, including classification, prioritisation, ownership assignment, and closure confirmation. It supports organisations seeking consistent handling of inbound enquiries while maintaining a clear audit trail for compliance and service-quality reporting.

Business Outcomes

  • Helps reduce response delays through automated confirmation and routing
  • Supports more consistent enquiry classification and prioritisation across teams
  • Improves visibility into enquiry ownership and status at every stage
  • Designed to strengthen accountability with a documented closure and audit trail
  • Makes it easier to capture post-closure feedback for service improvement

Workflow Steps

Steps

  1. 1
    Create Enquiry Recordcreate record

    Creates a record for the submitted product enquiry.

  2. 2
    Set Status to Openupdate record

    Marks the enquiry as Open on creation.

  3. 3
    Send Confirmation Emailsend email

    Sends an immediate confirmation email to the submitter.

  4. 4
    Check if Mobile Number Provided

    Sends a confirmation SMS only if a phone number was provided.

    phone: ""Send Confirmation SMS
    DefaultClassify Enquiry
  5. 5
    Send Confirmation SMSsend sms

    Sends a confirmation SMS to the submitter's mobile number.

  6. 6
    Classify Enquiryai classification

    Categorises the enquiry to determine whether it's a sales lead, product/technical question, support-related, or general query.

  7. 7
    Route by Enquiry Category

    Routes to human review if AI confidence is low, otherwise proceeds to prioritisation.

    _ai_clf_classify_enquiry_needs_human_review: "true"Manual Classification Review
    DefaultPrioritise Enquiry
  8. 8
    Manual Classification Reviewcreate task

    Low-confidence classification: an internal reviewer confirms the enquiry category before assignment.

  9. 9
    Prioritise Enquiryai prioritisation

    Assesses purchase intent and urgency to prioritise high-intent requests.

  10. 10
    Check Prioritisation Confidence

    Routes low-confidence prioritisation to human review before assignment.

    _ai_priority_prioritise_enquiry_needs_human_review: "true"Manual Priority Review
    DefaultAssign to Sales or Product Contact
  11. 11
    Manual Priority Reviewcreate task

    Low-confidence prioritisation: an internal reviewer confirms urgency before assignment.

  12. 12
    Assign to Sales or Product Contactassign user

    Assigns the enquiry to the appropriate sales or product contact for response.

  13. 13
    Set Status to Assignedupdate record

    Updates the enquiry status to Assigned.

  14. 14
    Respond to Enquirycreate task

    The assigned contact answers the enquiry and records their response notes.

  15. 15
    Record Response and Close Enquiryupdate record

    Persists the response notes to the record and marks the enquiry as Closed.

  16. 16
    Send Closure Confirmation Emailsend email

    Notifies the submitter that their enquiry has been answered and closed.

  17. 17
    Wait 1 Day Before Feedback Request

    Pauses for 1 day after closure before requesting feedback.

  18. 18
    Send Feedback Requestrequest external input

    Sends a short feedback request to the submitter about how their enquiry was handled.

  19. 19
    Set Status to Respondedupdate record

    Updates the enquiry status to Responded once the assigned contact has answered.

Fields

  • Full Name*
  • Email Address*
  • Phone Number (optional)
  • Product of Interest*
  • Your Question or Message*
  • Enquiry Status
  • +1 more fields

Forms

Product Enquiry

5 fields

Data Views

All Product Enquiries

full_name, email, product_of_interest, enquiry_status +1 more

Dashboard Widgets

Enquiry Status OverviewEnquiries by Product of InterestRecent Enquiries

Recommended integrations

Setup the following integrations to extend workflow capability.

  • Send SMS in the workflow

    Twilio logoTwilioAWS SNS logoAWS SNS
  • Send email in the workflow

    AWS SES logoAWS SES
product enquiry formproduct inquiry formproduct contact formproduct question formproduct information request

Similar Workflows

Similar Categories

FAQs

How is this workflow audited?

Every step in the workflow, from record creation to closure and feedback, is logged within assess.one, creating a timestamped history of status changes, classifications, assignments, and manual reviews. This gives compliance and management teams a traceable record of how each enquiry was handled without needing to build separate reporting tools. Audit logs can be reviewed at any time by users with appropriate permissions.

Who has access to enquiry records and responses?

Access is managed inside assess.one through role-based permissions, so only assigned sales or product contacts, reviewers, and administrators can view or act on a given enquiry record. Manual classification and priority review steps can be restricted to specific roles to support segregation of duties. Administrators can adjust access levels at any time as team structures or responsibilities change.

How does this integrate with email and SMS notification systems?

Email and SMS notifications, such as the confirmation, closure, and feedback request messages, are configured directly within assess.one rather than through separate third-party integrations. Notification templates, triggers, and conditional logic (such as sending SMS only when a mobile number is provided) can be set up and adjusted inside the platform. This keeps notification management centralised alongside the rest of the workflow.

Can the classification and prioritisation logic be customised?

Yes, the classification and prioritisation steps, including the confidence thresholds that trigger manual review, can be customised directly in assess.one to reflect an organisation's product categories, priority tiers, or risk criteria. Teams can adjust routing rules so enquiries are directed to the correct sales or product contact based on category or urgency. Changes take effect immediately without requiring redevelopment.

What happens when a manual classification or priority review is triggered?

When the system's confidence in an automated classification or priority assignment falls below a configured threshold, the enquiry is routed to a manual review step for a designated reviewer to confirm or adjust. This step helps reduce misrouted or mispriotised enquiries while keeping the majority of straightforward cases moving automatically. Reviewers can update the classification directly within the workflow before it proceeds to assignment.

Who typically needs access to this workflow?

Sales representatives, product specialists, customer service teams, and their managers typically need access, along with administrators responsible for configuring routing rules and notification settings. Compliance or quality assurance staff may also require read access to review closure records and audit trails. Access can be scoped tightly so each role only sees the information relevant to their responsibilities.

What compliance or approval considerations apply to this workflow?

Because the workflow captures personal contact details such as name, email, and phone number, organisations should consider data retention and consent policies when configuring the intake form and downstream steps. Manual review checkpoints for classification and priority support additional oversight for enquiries that may carry higher business risk. The closure step provides a documented approval point confirming the enquiry has been fully addressed before feedback is requested.

How long does implementation take?

This workflow template is ready to use, so it can be reviewed, adjusted, and published within minutes rather than requiring a lengthy implementation project. Once published, the live process is available immediately for sales and product teams to start managing incoming enquiries. Further adjustments to steps, roles, or notifications can be made directly in assess.one at any time without downtime.

What happens if an enquiry doesn't receive a response before closure?

The workflow requires a recorded response at the 'Respond to Enquiry' step before the enquiry can move into the closure stage, helping prevent premature closures. Status tracking (Open, Assigned, Closed) provides visibility into enquiries that may be stalled, supporting managers in identifying and escalating delayed cases. This structure is designed to support timely handling rather than guarantee a fixed response time.

Can the feedback request timing be adjusted?

Yes, the one-day wait period before the feedback request is sent can be modified directly within assess.one to match organisational preferences or customer experience policies. Teams can also customise the feedback request content or disable this step entirely for certain enquiry categories. Changes apply immediately to future enquiries processed through the workflow.

Ready to use this workflow?

Create a free account and customise this workflow for your business.

Product Enquiry Response Workflow | assess.one