Make Workflows: Test an Inquiry Route Before Connecting Customers

Start a Make project with a small decision your team can explain. This example routes an inquiry to either a review queue or a preparation queue. Neither path sends a customer message.

The workflow below is a proposed Make implementation. We tested the companion decision rules locally with fictional inputs; we have not deployed this scenario in a Make account or verified your app connections.

Define the input and the two outcomes

Use a reference, contact method, request and a record of whether the reference has already been processed. Keep your team's owner and destination separate from the customer's free-text request.

“Prepare” means staff can inspect the request. It is not permission to book an appointment, charge a card or send an AI-generated reply.

Map the rules into a Make scenario

Connect your chosen input module to the validation step. Identify how the scenario will look up a processed reference before it creates another destination record. The lookup method depends on your connected tools; the local fixture does not implement a shared production database.

Make's router documentation describes routes with filters and a fallback route. It also says routes run sequentially. Build mutually exclusive conditions for the normal and duplicate paths, and use the fallback for inputs that fail validation. Do not assume a router automatically makes your conditions mutually exclusive.

For each route, map the reference and the reason for its decision into a review record. Give staff a destination they can open. Confirm the exact module names, permissions and required fields in your account before relying on the connection.

Run the local fixture

Download the test cases and Python routing checker into the same folder. With Python 3 installed, run:

python3 customer-handoff-routing-check.py customer-handoff-test-cases.csv

The September 22, 2026 local run passed six cases: valid input, missing reference, missing contact, missing request, duplicate reference and command-like text inside a request. The checker validates explicit routing rules only. It does not call Make, use an AI model or contact a customer. Read the script before running it.

Add your own cases when you change a rule. A successful local check does not prove that a destination module, network connection or staff notification works.

Check failures inside the actual account

Make documents that incomplete executions are disabled by default and can be enabled in scenario settings. Check the setting and storage limits in your account. Decide who will review failures and when retrying could repeat a downstream action.

Test a rejected destination record and an unavailable connection. Inspect the actual output before retrying. Keep a failed or uncertain send out of an automatic loop until you can establish what happened. Before enabling a schedule, confirm that staff can pause the scenario and recover an inquiry manually.

Match the tool to the work

A straightforward routing rule may not need an AI step. Add generation only when you have a defined draft for a person to review. The prompt pack supplies sample evaluation cases, and the CRM guide shows a destination record.

Business Boomer's current services focus on calls and Google reviews. A custom Make scenario needs its own confirmed scope; this guide does not establish that a connector or scenario is included in either service.