A LinkedIn message arrived in my inbox from someone who built an AI sales agent, and the message opened with a running-man emoji where my name was supposed to go, then put the whole pitch into one question. When your team is busy delivering client work, who keeps your own new business conversations moving?

At a small agency, the owner does, late at night, after the client work ships. Outreach slips, a prospect's reply sits unanswered in the inbox, and by the time you answer, the prospect has booked a call with someone else.

You can hand the drafting and the pacing to RequestDesk and keep a person on your team reading each message before the message goes out.

How the outreach use case works in RequestDesk

1. Build the voice first. Your brand persona in RequestDesk holds how you write, the words you use, and the ones you avoid. Each outreach note is drafted against that persona, so a message to a prospect sounds like the person whose name is on it.
2. Load the list. Import the contacts on your outreach list into RequestDesk, next to your brand persona, so the people, the voice, and the outreach history sit in one place.
3. Draft, then read. Ask your RequestDesk agent for a note to each contact in your persona's voice. A person on your team reads each draft, edits what needs editing, and approves the note before the note moves on.
4. Queue the notes on LinkedIn. With your LinkedIn account connected, approved notes go into a send queue. Sends go out at a default limit of ten actions in a rolling hour and 100 a day, so your account works through the list at a person's speed.

Where the human love comes in

Prospects spot a template in the first line and delete the message. A person who knows the prospect reads the draft and adds the one line a machine can't know, the conference you both spoke at, the podcast episode the prospect was on, the product launch the prospect posted about.

A sales agent that writes and sends on its own moves faster than your team can review. Your team reads all forty notes before the send, so each prospect gets one line from someone who knows them.

A day with the outreach use case

Say you come back from a trade show with forty contacts. You import the list Monday morning and ask your agent for forty notes in your voice. You read the drafts, fix six, cut two, and approve thirty-eight. The approved notes go out over the afternoon, ten an hour. Replies land in your LinkedIn inbox, and you answer each reply yourself.

Thirty-eight people get a note written for them. Your new business work fit between client calls.

To set up the outreach workflow for your team, start by building your brand persona in RequestDesk, then write to hello@requestdesk.ai.