Skip to content
Splice Work

Meet Beep Beep

An AI appointment setter that follows up until it books.

Most outreach tools wait for you to log in. Beep Beep is an AI email agent that starts the conversation: it asks in Slack whether you want a campaign, finds the people, researches each one, writes every email itself, follows up three times, and tells you the moment someone sounds interested.

Beep BeepAppSunday, 11:20 PM

Ready for a new campaign?

Hey Chase — ready to get a campaign going? Nothing is lined up for Tuesday yet. Say the word and I’ll find 12 people from your saved targeting and take it from there.

Titles
CEOs, founders
Industries
Food and beverage manufacturers
Employees
1–200
Locations
South San Francisco, Bay Area
Source order
Salesforce first, then approved shortfall
Paid ceiling
10 ZoomInfo credits
Yes, set it upAdjust settingsEmail template

No lead search, credit spend, CRM write or email has started. Or just tell me: “remind me tomorrow”, “not this week”, “stop suggestions”.

The AI appointment setter goes first.

This is the part that surprises people. Every other AI appointment setter waits for you to open it. On a Sunday evening this one notices nothing is scheduled and asks. Answer in ordinary language and it adjusts.

You, in the thread

“Send it to food manufacturers in South San Francisco.”

Beep BeepAppMonday, 6:40 PM

Got it — updated your targeting. titles: CEOs, founders; industries: food manufacturers; locations: south san francisco. Lining up a fresh campaign on that now.

Lined one up — it’s in the campaign card in the channel. Say yes there and I’ll start the research.

What happens after you say yes

It does the research before it writes a word.

Four systems, in this order, every campaign. The order matters: your own data is free and the paid sources are capped.

  1. 01

    Salesforce

    Your own CRM first, always. It pulls contacts you already own that match the targeting, so you are not paying to rediscover people who are sitting in your database.

  2. 02

    ZoomInfo

    Only if the list comes up short, and only up to a credit ceiling you set. The campaign card shows the ceiling before you approve it, so a run can never quietly burn a month of credits.

  3. 03

    Firecrawl

    Reads each company's actual website at send time. This is where the specific sentence in every email comes from, rather than a merge field with a company name dropped into it.

  4. 04

    NeverBounce

    Verifies every address before a single message goes out. Bounces are what wreck a sending domain, so the check happens first, not after the damage.

Three waves, then it stops

Persistence with an end date.

Wave 1

The first email

Written per person from the research, scheduled for 8:00 in each recipient's own timezone. Not your morning, theirs.

Wave 2

The follow-up, and their boss

For anyone who did not reply, it writes a second message referencing the first. It also finds that person's manager and writes to them too, so the thread has somewhere to go if the first contact is the wrong one.

Wave 3

The last one

A final short message, then it stops. No indefinite drip, no eleventh touch six weeks later that makes you look desperate.

GmailSent mail8:00 AM, recipient’s own timezone

RE: Harbor Provisions AI integration opportunities

Chase Gonzales<chase@splicework.ai>
to Dana Whitfield

Hi Dana,

I reached out to your team a while ago and didn’t hear back. I’m interested in discussing how your focus on governed and auditable agents aligns with the evolving needs of enterprises in AI integration.

Would you have a moment to chat about this? If it’s easier to talk it through, here’s my calendar: splicework.ai/book

Chase

Splice Work · California, United States

A real wave-two email, with the recipient and their company swapped for stand-ins. The second sentence came from research the agent did on that company’s own website at send time.

Every email is written for one person

There is no template with a first-name token. The agent reads that company’s site and writes a sentence that could only have been written to them. That is why twelve emails beat two thousand.

It also sends at 8:00 in the recipient’s timezone rather than yours, which is the difference between landing at the top of a morning inbox and landing at 4am.

Scheduling, in its own words

“12 emails written and scheduled for 8am in each person’s own timezone. Nothing needs approving; say stop to hold them.”

When someone replies

It reads the replies and hands you the good ones.

An AI email agent is not trying to close anybody. Its job is to get a real human conversation started and then get out of the way.

Beep BeepAppThursday, 3:02 PM

⭐ 🎉 Dana Whitfield sounds interested!

Thanks for following up — we’re interested over here. Could we schedule a call for Tuesday or Wednesday morning?

You may want to take this over — open the conversation and reply as Chase.

Beep BeepAppFriday, 8:00 AM

🎉 Your campaign is finished!

All three waves are out.

  • Sent:12
  • Replied:1
  • Bounced:0
  • Asked to come off the list:0
  • No response yet:11

Counted from the send log. Inbox placement is unknown without a seed test.

That last line is the point

Every outreach tool on the market will quote you an open rate. Open tracking has been unreliable since mail clients started pre-fetching images, and inbox placement genuinely cannot be known without a seed test. So the agent reports what it can actually count, and says so. You will get fewer impressive numbers from us and more true ones.

Staying out of spam, and out of trouble

Two ways cold email goes wrong, and what the agent does about each.

Deliverability

Landing in spam is mostly a reputation problem, and reputation is mostly a bounce problem. Every address is verified before the campaign starts, which is why the wrap-up card can report zero bounces rather than hoping for them.

  • Addresses verified before the first send, not after
  • Small, researched batches instead of thousands of generic sends
  • Sent from your own warmed domain, through your own mailbox
  • Anyone who asks to come off the list is removed immediately

Tone

The other failure is an email that is obviously machine-written: three paragraphs of flattery, a fake compliment about a recent funding round, and a close that nobody says out loud. The agent writes short, says why it is writing, and asks one question.

  • One specific sentence drawn from that company's own site
  • No invented praise and no fabricated shared connection
  • A single ask, usually fifteen minutes
  • You set the template and the voice; you can change it in the thread

Guardrails

What this AI email agent will never do.

  • Search for leads before you say yes
  • Spend a data credit above the ceiling you set
  • Write to anyone who asked to come off the list
  • Send from a domain it has not warmed
  • Claim an open or a read it cannot actually measure
  • Keep going after wave three
Writes the campaign, every contact and every wave back to Salesforce
Keeps a per-campaign sheet with every email it sent, in full
Removes anyone who asks, immediately, without checking with you
Runs in Slack today, and in Microsoft Teams the same way
Stops the moment you say stop, mid-campaign included

Where it works

  • Slack
  • Microsoft Teams
  • Salesforce
  • ZoomInfo
  • Apollo
  • Firecrawl
  • NeverBounce
  • Gmail

AI appointment setter questions we get asked

What makes this an AI appointment setter rather than a mail-merge tool?

A sequencer sends what you wrote to a list you uploaded. This one decides who to write to from your CRM, researches each company, writes each message from that research, verifies the address, reads the replies, and tells you which ones are worth your time. You approve the campaign; it does the work.

Does it email people without asking me first?

No. The campaign card in Slack shows the targeting, the number of people and the credit ceiling, and nothing at all happens until you press yes. No lead search, no credit spend, no CRM write and no email before that click.

What happens when someone actually replies?

It reads the reply, and if it sounds like interest it posts the message in Slack and tells you to take it over. It does not try to negotiate, price or book on your behalf. Where a reply is an unsubscribe, it takes them off the list and updates Salesforce without asking you.

How is this different from an AI SDR?

Most tools sold as an AI SDR want to own the whole pipeline and live in their own dashboard. This agent lives in Slack, uses the CRM you already pay for, and hands a human the conversation the moment it becomes a conversation.

Can it work in Microsoft Teams instead of Slack?

Yes. Slack is where it runs today because that is where the first customers work. Teams is the same pattern: a card, a yes, and a thread per campaign.

Will this hurt our sending domain?

That is exactly why address verification runs before the first send and why the volumes are deliberately small. A campaign of twelve well-researched emails is safer and works better than two thousand generic ones.

What does it write back to the CRM?

The campaign, every contact it touched, which wave each person received, the reply status, and the unsubscribes. The whole run is auditable in Salesforce and in a per-campaign sheet, so nothing lives only inside the agent.

What is the AI email agent actually running on?

Hosted frontier models through their business APIs for the writing and the reply reading, your Salesforce for the truth about contacts, and the research tools named above. We do not train models on your data.

Want Beep Beep working your inbox?

Tell us who you sell to and which CRM you run. We'll show you a campaign on your own data before you commit to anything.