# Messages you can adapt, and what to show in the demo

I'd use these as a starting point and change them based on who you're talking to. Replace the brackets with real details. I haven't attached a conversion rate to these scripts, and you should only say you've built something if you can show it.

## A quick thing about templates

I know this sounds a bit ironic because I just gave you a template, but **be yourself when you reach out**. People buy from people. The person reading your message should feel like there's a real human on the other side who has a reason to talk to them.

You can write the message yourself. A template can help when you're staring at a blank screen, but copying a set of words doesn't mean your outreach will suddenly work ten times better. **Be natural, be straightforward, and say why you're reaching out.** If a line sounds weird when you say it out loud, change it. I'd use the example to get started, then put it in your own words.

## First email

Subject: after-hours requests at [Business]

Hi [Name],

I saw that [Business] asks customers to call for [service]. How do you handle those calls after closing?

I built a small demo that collects the job details and callback number, then sends the request to your team. Would a short walkthrough be useful?

[Your name]

Use the second paragraph only after building the demo. Contact relevant business recipients, use accurate sender details and respect requests to stop. Check the rules that apply to your outreach; this template is not a permission to bulk-message people.

## Instagram DM

hey [name], i had a look at how you take inquiries for [specific offer].. do you handle the qualification and booking yourself in the dms?

ive put together a small example of how the questions and handoff could work. would it be useful if i sent it over?

Only use this when you have a relevant example. Do not claim you can see their inbox, unanswered messages or sales results.

## If you follow up

Hi [Name], a bit more context on the demo: it collects [specific details] and sends them to [agreed destination]. Your team would still handle [next step]. Is that something you want help with, or have you already got it covered?

Choose a reasonable follow-up schedule for the channel and recipient. Stop after an opt-out. Do not send the same follow-up indefinitely.

## Demo recording outline

1. Situation: "This example handles a routine request when the office is closed."
2. Show the caller providing the job details and confirming the callback number.
3. Show the resulting request in your test inbox. Use fictional details.
4. Explain the handoff: "Your team still confirms the callback and any appointment."
5. Name the limits: "This version does not book slots or dispatch emergencies."
6. Ask: "How would that request need to reach your team to be useful?"

Use only synthetic records or material you have permission to share. Close private tabs and hide credentials before recording.

## Things to ask when you talk

- Can you walk me through a recent inquiry from start to finish?
- Who handles it, and where do the details go?
- Which requests can wait, and which need a person immediately?
- What information do you need before calling someone back?
- What do you use now, and what is inconvenient about it?
- Who will monitor the handoff if we test this?
- What would a useful pilot result look like in your own records?
- Who approves the scope and pays for the accounts?

## Common replies

"We already have someone." Ask when they are unavailable and whether any coverage gap remains. If the process works, acknowledge that and move on.

"Send details." Send the short demo and a clear description of what it does. Ask one question needed to judge fit, rather than attaching an entire agency brochure.

"How much?" Explain the small pilot scope you can price, the inputs you still need, and which usage costs sit outside your fee. Do not dodge the question with a mandatory long call.

"Can you guarantee customers?" Explain the observable result you can test, such as requests reaching a monitored inbox. Do not promise control over attendance, the owner's callbacks, or sales conversion.

"No thanks." Acknowledge and mark do-not-contact. Do not turn refusal into a sequence of rebuttals.

## Keep a record as you go

Keep separate counts for businesses contacted and messages sent. Then track delivery failures, replies, useful conversations, demos, proposals, paid pilots, and anyone who asks you to stop. When you change something, write down what and when. With a small number of messages, I'd be careful about treating the reply rate as something you can expect every time.