A Front Desk That Answers at 2am
Build a custom GPT that handles your twenty most common questions.
Eighty percent of first contacts are the same six questions about hours, price, location, and availability. Answering them personally is not service, it is a bottleneck.
That is the gap this drop closes. It is a automation skill built for ChatGPT, and it takes about ten minutes to set up the first time. After that it runs in under a minute.
Who should use it
Clinics, salons, schools, and service businesses with repetitive enquiries.
How it works
The skill file does five things, in this order.
1. Collect the actual questions. From WhatsApp and DMs, in the customer's own wording.
2. Write answers, not policies. The customer wants the price, not your pricing philosophy.
3. Set the escalation rule. Exactly when it must hand over to a human, stated first.
4. Lock the scope. It must refuse medical, legal, and pricing exceptions.
5. Test with the awkward ones. Complaints, refund demands, and questions you cannot answer.
What comes back
Custom GPT instructions, a knowledge file, escalation rules, and a test script.
The mistake to avoid
Write the escalation rule before the answers. Deciding in advance what it must never handle is what keeps a helpful assistant from confidently inventing a refund policy.
Running it
Paste the prompt into the Instructions field of a new custom GPT, or use it directly in a chat. If the task involves files, turn on the code interpreter so calculations are executed rather than estimated.
Where this fits
On its own, one skill saves an hour a week. The compounding happens when three or four of them run in sequence on the same input, the same transcript that produces a scope of work also produces the follow-up email and the project brief. That is the point at which it stops being a prompt and starts being an internal tool. If you want that wired into the systems your team already uses, that is the work 67 Digital does.
In the file
Write instructions for a customer-facing custom GPT.
<business>{what you do, hours, locations, price ranges, booking method}</business>
<real_questions>{paste 20 actual customer messages, unedited}</real_questions>
Structure the instructions in this order:
1. ESCALATION RULES FIRST, the exact situations where it must stop and hand
over to a human, with the handover message. Include complaints, refunds,
medical or legal questions, pricing exceptions, and anything about a
specific existing order it cannot verify.
2. SCOPE, what it answers and what it refuses. Refusals must be warm and
include the human contact route.
3. TONE, matched to these examples of how we write: {paste 3 real replies}
4. ANSWERS, for each of the 20 real questions, the answer in under 60 words.
5. NEVER, a list of things it must never do: invent prices, confirm
availability it cannot check, give a time estimate, or apologise for policy.
Then write 10 adversarial test messages and the correct response to each.