Callcraft Studio
Still Air / Enquiry workflow demonstration

Every enquiry.
A next step.

An installation request needs a different handover from a repair. Try the capture, assignment and follow-up, then see what happens when a connection fails.

Try the handover

Still Air is a fictional heating and cooling business. This demonstration uses sample data in this tab. Nothing is sent to an email provider or a CRM.

01 / Follow the request

A small form.
A clear handover.

Choose a job and coverage.
The next action follows the rules.

Still AirInstallation · Repair · Maintenance
Sample customer

customer@example.com

A reserved example address. No personal details needed.

The interactive controls load with JavaScript. The rules and handover are explained below.

The handoverReady to try

No sample request yet. Choose a job and coverage to begin.

  1. 01

    Capture the request

    Waiting for the sample form.

  2. 02

    Assign the owner

    The job and coverage set the route.

  3. 03

    Acknowledge the enquiry

    A preview in the sample inbox.

  4. 04

    Keep the next action visible

    A task your team can review or stop.

This is a local demonstration of the rules and recovery paths. A client build needs approved tools, permissions, message wording and a responsible team member. Refreshing this page clears the sample record.

02 / The rules behind it

Agree the rules.
Keep a person in control.

  1. Installation goes to the installation desk. Repairs and maintenance go to the service desk. An outside-area request goes to coverage review.
  2. A repeated request keeps the same record. In this example, the same job and coverage identify the sample request. A client workflow needs its own agreed duplicate key.
  3. A failed connection keeps the request. Retry uses its original ID, or the assigned owner takes over manually.
  4. Follow-up can be stopped. The task is cancelled. An acknowledgement already in the sample inbox remains visible.
03 / From example to your tools

What belongs
in a real build?

Does this connect to our CRM?

This demonstration runs locally with sample adapters. Your project starts by checking the actual CRM, subscription level, connector support and access permissions.

Can the messages be changed?

Yes. You approve the wording, timing and permission rules. Acknowledgement, quotation follow-up and marketing messages are different purposes and need their own agreed handling.

What does the starting workflow include?

One trigger, up to five actions, at most one decision branch and two supported applications. Failure checks, operating instructions and a handover are included. Software and ongoing care are separate.

Your enquiry process

Where does the
handover break?

Tell us what receives the request, who handles it and what happens next.

Discuss one workflow