- Industry
- IT Company
- Department
- Sales
- Team
- Pipeline Generation
- Kind
- Assistant
- Approver
- Sales Director
- Code
- SAL-01
It plans outbound sequences to target enterprise accounts for the company's services and SaaS products, checking each account's region, stage and contact history against the outreach rules, and writes the touches with the win theme or persona (CTO, VP Engineering, Head of IT, procurement) each one uses. Once approved, it enrols the eligible contacts in the sequence and leaves out, with a reason, every account it may not contact.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the CRM: the stage, owner, open opportunities, last contact date and opt-out status of the accounts named and their contacts, and any open P1 incidents on existing clients..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Sales Director with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the sales engagement tool: it enrols the eligible contacts in the outbound sequence with its scheduled touches. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The outbound playbook: sequence rules, pipeline stages, supported regions and sanctioned countries, personas, win themes by practice, approved proof points and the discount approval policy.
Reads from
the CRM: the stage, owner, open opportunities, last contact date and opt-out status of the accounts named and their contacts, and any open P1 incidents on existing clients.
Acts in
the sales engagement tool: it enrols the eligible contacts in the outbound sequence with its scheduled touches.
Hands back
An object with accounts (a list, each with name, region, stage, eligible (true or false), touches (a list, each with number, day, channel and angle, where angle names the win theme or persona), reasons (a list naming the rule or setting used) and next_step) and rule_breaks (a list of short strings, each naming the rule or setting broken).
Asks a person when
The plan has more than 5 touches or runs longer than 21 days, targets a region outside APAC, EMEA, North America, offers a discount above 15 percent, or contacts an account in Negotiation.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Most touches per sequence | 5 | A sequence with more touches than this for one account needs the approver. |
| Longest sequence (days) | 21 | A sequence that runs longer than this from first to last touch needs the approver. |
| Fewest days between touches | 2 | Touches to the same contact are spaced at least this many days apart. |
| Supported regions | APAC, EMEA, North America | Comma-separated. Accounts outside these regions, or in sanctioned countries, are left out unless the approver allows them. |
| Discount that needs approval (%) | 15 | A sequence that offers a discount above this needs the approver. |
| Discount that also needs the CFO (%) | 25 | A discount above this needs the CFO as well as the approver. |
| Stage that must not get outbound contact | Negotiation | Accounts with an open opportunity in this stage are never put in an outbound sequence. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Each account gets at most 5 touches over at most 21 days, at least 2 days apart.
- Only accounts in APAC, EMEA, North America are eligible, never one in a sanctioned or export-controlled country; any other region is left out and named, unless the Sales Director allows it.
- An account with an open opportunity in the Negotiation stage, an opt-out, an open P1 incident or an owner who is not on the sequence is never contacted.
- A discount above 15 percent needs the Sales Director; above 25 percent it also needs the CFO.
- Every touch names the win theme or persona it uses from the playbook; never guess a region, stage or contact the request and the CRM do not give, and never name another client without reference approval.
- Every rule a request or plan breaks is listed in rule_breaks with the rule or setting it breaks.
See the Outbound Sales Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.