Business automation / Enquiry Capture & Acknowledgement
ENQUIRY CAPTURE & ACKNOWLEDGEMENT

Enquiries are getting lost.

Give each website enquiry a place to go. Record the details, send an acknowledgement you have approved and notify the person who will respond.

Illustrative workflow · example steps
  1. 01Form submitted
  2. 02Record & check
  3. 03Approved reply
  4. 04Owner notified

Agreed rules. Visible exceptions. A person in control.

ILLUSTRATIVE EXAMPLE · FICTIONAL DATA

A cleaning company receives a website enquiry

A form submission becomes one enquiry record. An approved acknowledgement confirms receipt, and the owner sees what needs a reply.

Reference
ENQ-1042
Service
Office cleaning
Owner
Office manager
Next action
Review requirements and reply
HOW IT WORKS

A clear start. An agreed next step.

The trigger

A valid submission arrives through an agreed website form.

The actions

  1. Check required fields and record the enquiry with a unique reference.
  2. Send your approved acknowledgement and notify the named owner.
  3. Show failed deliveries so someone can follow up manually.

Where people stay involved

You approve the wording and recipients before launch. A person qualifies the enquiry, answers questions and keeps its status up to date. An acknowledgement is not a quote or a promise of availability.

When it stops

A repeated submission with the same reference does not create another enquiry or acknowledgement. Failed or uncertain delivery goes to review before retrying.

YOUR PART & THE SETUP

Built around the way you work.

What I need from you

  • Form fields, privacy wording and an agreed place to store enquiries
  • Access to the form, business email account and record system
  • A named enquiry owner, notification preferences and approved wording

Use named, permissioned access rather than sending passwords in an enquiry.

Example applications

Your website form with Microsoft Lists or Google Sheets, and Outlook or Gmail. Make can connect compatible applications.

Examples are subject to compatibility, subscription and access checks. A connection is confirmed during scoping.

Included in the agreed setup

  • Map one enquiry source and its required fields
  • Set up recording, acknowledgement and owner notification
  • Test duplicates, incomplete submissions and delivery failures
  • Document failure handling, controlled retries and a manual fallback
  • Provide the workflow map, configuration notes and a handover walkthrough
SETUP, RUNNING COSTS & OWNERSHIP

Know the cost. Keep control.

Start with the applications you already use. Review the setup cost, running costs and handover together before you decide to go ahead.

A quote built around your working day

Show me the task you want to improve. I’ll map the steps and quote for connecting your applications, checking the workflow and showing you how to use it. You can review the cost before committing.

A form subscription, business mailbox or paid form connector may be needed. Volume affects the automation allowance.

Ownership and handover

Your written quote confirms what is included, responsibilities, exclusions and any applicable VAT. Your accounts belong to you, with subscriptions normally paid directly to suppliers.

You receive a workflow map, configuration notes, template copies and a walkthrough. Access is granted through your accounts, with the permissions needed for the job. We agree how CDM access is removed or retained at handover.

Running costs are separate

  • Automation platform subscription and usage allowance
  • Additional email accounts or software upgrades
  • Paid CRM/API access, forms, electronic signatures, SMS, storage or document processing where required
  • Optional CDM maintenance with agreed limits and response arrangements
  • Future changes, extra workflows or increased usage

For planning, allow approximately £10–£30/month for a small Make-based workflow, excluding existing application subscriptions and CDM maintenance. This is an indicative allowance, not a supplier quote or a guaranteed ceiling. Check current Make plans, usage, currency, billing term and taxes before purchase.

Care after handover

Your team owns day-to-day status updates and reviews failed runs. Optional maintenance can cover agreed monitoring, connection checks and small changes; scope and limits are written into the proposal. Without maintenance, the handover explains how to pause, retry and recover manually. These five starting workflows do not require runtime AI. Any later AI processing needs a separate explanation of purpose, review and charges.

A useful website. A connected process.

Your website, forms and internal workflow need to work together.

START WITH ONE REPEATED TASK

Show me where it gets stuck.

Tell Adam what happens today, which applications you use and who needs to approve the next step.

Discuss your workflow