Workflow Template
Billing Enquiry Contact Form Workflow
Public website billing enquiry contact form and lightweight workflow: captures submitter details, sends immediate confirmation, classifies and prioritises the enquiry, assigns it to a finance or customer service owner, records the resolution, closes the enquiry with a closure email, and follows up with a feedback request the next day.
Billing enquiries that land in a shared inbox get missed, misfiled, or bounce between finance and support with no owner and no record of resolution. The Billing Enquiry Contact Form Workflow captures every submission the moment it's filed, sends instant confirmation, classifies and prioritises it automatically, and routes it to the right owner — with manual review triggered only when confidence is low. Teams get a closed-loop process from first contact to resolution and feedback, with every step logged and nothing falling through the cracks.
Business Outcomes
- Helps reduce time-to-first-response with immediate confirmation emails and SMS
- Supports faster triage by auto-classifying and prioritising enquiries before a human touches them
- Reduces misrouted enquiries by assigning based on classification and priority confidence
- Improves accountability with status tracking from received to assigned to resolved
- Supports higher closure quality by capturing feedback the day after resolution
Workflow Steps
Steps
- 1Create Billing Enquiry Recordcreate record
Creates the billing enquiry record from the submitted form.
- 2Set Status to Receivedupdate record
Marks the enquiry as received.
- 3Send Confirmation Emailsend email
Sends an immediate confirmation email to the submitter.
- 4Check if Mobile Number Provided
Determines whether to send a confirmation SMS.
phone: ""→Send Confirmation SMSDefault→Classify Billing Enquiry - 5Send Confirmation SMSsend sms
Sends a confirmation SMS to the submitter's mobile number.
- 6Classify Billing Enquiryai classification
Uses AI to categorise the enquiry based on type and message content.
- 7Route on Classification Confidence
Routes low-confidence classifications to human review before proceeding.
_ai_clf_classify_enquiry_needs_human_review: "true"→Persist Category Pending ReviewDefault→Persist Category - 8Persist Category Pending Reviewupdate record
Saves the AI-suggested category flagged for human confirmation.
- 9Persist Categoryupdate record
Saves the AI-assigned category to the record.
- 10Assess Priorityai prioritisation
Assesses urgency for time-sensitive or payment-blocking issues.
- 11Route on Priority Confidence
Routes low-confidence priority assessments to human review.
_ai_priority_prioritise_enquiry_needs_human_review: "true"→Request Manual Priority ReviewDefault→Assign to Finance or Customer Service Owner - 12Request Manual Priority Reviewrequest approval
Asks a supervisor to confirm priority when AI confidence is low.
- 13Route on Priority Confirmation
Proceeds to assignment if the supervisor confirms the AI priority, or escalates for manual resolution if rejected.
approval_status: "approved"→Assign to Finance or Customer Service Ownerapproval_status: "rejected"→Escalate Priority DisagreementDefault→Escalate Priority Disagreement - 14Assign to Finance or Customer Service Ownerassign user
Assigns the enquiry to the appropriate owner based on category.
- 15Set Status to Assignedupdate record
Marks the enquiry as assigned to an owner.
- 16Investigate and Respond to Enquirycreate task
Owner investigates the billing enquiry and records the response or correction made.
- 17Route on Resolution Outcome
Checks whether the enquiry is resolved or needs further information from the customer.
enquiry_resolution_outcome: "Resolved"→Record Response and Set Resolvedenquiry_resolution_outcome: "Needs Further Information"→Request Further Information from SubmitterDefault→Record Response and Set Resolved - 18Request Further Information from Submitterrequest external input
Asks the submitter to provide additional details needed to resolve the enquiry.
- 19Return to Owner for Further Handlingrestart from step
Restarts the handling task now that further information has been provided.
- 20Record Response and Set Resolvedupdate record
Persists the response/correction notes and marks the enquiry resolved.
- 21Close Enquiryupdate record
Marks the enquiry as closed once resolved.
- 22Send Closure Confirmation Emailsend email
Notifies the submitter that their enquiry has been closed.
- 23Wait 1 Day Before Feedback Request
Pauses for one day after closure before requesting feedback.
- 24Send Feedback Requestrequest external input
Sends a short feedback request to the submitter about how their enquiry was handled.
- 25Escalate Priority Disagreementcreate task
Supervisor rejected the AI-suggested priority; manually confirm the correct priority before assignment.
Fields
- Full Name*
- Email Address*
- Mobile Number (optional)
- Customer or Account Reference
- Invoice or Transaction Reference (if relevant)
- Enquiry Type*
- +4 more fields
Forms
Billing Enquiry
7 fields
Data Views
Billing Enquiries
full_name, email, enquiry_type, enquiry_category +3 more
Dashboard Widgets
Recommended integrations
Setup the following integrations to extend workflow capability.
Send SMS in the workflow
Twilio
AWS SNS
Send email in the workflow
AWS SES
Similar Workflows
Similar Categories
FAQs
What happens if the billing enquiry classification confidence is low?
The workflow routes low-confidence enquiries to a 'Persist Category Pending Review' step instead of auto-assigning them. A team member reviews and confirms the category before the enquiry moves forward. This keeps automated routing accurate without forcing every enquiry through manual review.
Can this handle enquiries where no mobile number is provided?
Yes. The workflow checks for a mobile number before attempting to send a confirmation SMS, and skips that step automatically if none was provided. The confirmation email still sends regardless, so the submitter always gets acknowledgement.
What if the priority assessment isn't confident enough to auto-route?
When priority confidence is low, the workflow triggers a manual priority review step and waits for confirmation before assigning an owner. Once confirmed, it routes based on the reviewed priority. This prevents urgent enquiries from being under-prioritised or low-priority ones from jumping the queue.
What happens if the owner needs more information from the submitter?
If the resolution outcome indicates missing information, the workflow triggers a 'Request Further Information' step that contacts the submitter directly. Once a response comes back, the enquiry returns to the owner for continued handling rather than sitting unresolved. The status and history stay visible throughout.
Who needs access to this workflow?
Finance and customer service staff who investigate and respond to enquiries need access as assignees, along with anyone responsible for reviewing low-confidence classifications or priorities. Managers who need visibility into enquiry status and resolution records can be given read or oversight access. Access levels are configured directly inside assess.one.
Can we customise the routing logic or add more classification categories?
Yes. Steps like classification, priority assessment, and routing rules are all editable inside assess.one, so teams can add categories, adjust confidence thresholds, or change who enquiries route to. Notification content and timing, including the confirmation email and next-day feedback request, can also be customised without any external development work.
How long does it take to get this workflow live?
The template is ready to use, so publishing it takes minutes, not weeks. Once published, the finance and customer service team can start receiving and handling live billing enquiries immediately, with steps and roles adjusted on the fly as needed.
Does the workflow keep a record for compliance or audit purposes?
Yes. Every step — from record creation through classification, assignment, resolution, and closure — is logged with status changes, so there's a traceable history for each enquiry. This supports internal audit needs and gives managers a clear view of how enquiries were handled and by whom.
What happens after an enquiry is resolved?
Once the owner records a response, the workflow sets the enquiry status to resolved and sends a closure email to the submitter. The next day, it automatically sends a feedback request, closing the loop without requiring manual follow-up from the team.
Ready to use this workflow?
Create a free account and customise this workflow for your business.
