A template is a job an agent runs for your workspace, such as keeping every campaign stocked with leads. Each ready template is a Ken skill your AI tool loads from Ken, with a starter prompt to paste into the tool. To set up your tool, see Run Ken's agent templates in your own AI tool.
In Ken, the same list is under Outreach, then Agent team, then Templates. Run in your own tool on a ready template walks you through the setup and copies its starter prompt.
The rails
Every template follows the same rules, whichever tool runs it:
- Change campaigns only through
agent_team. The agent asks Ken for each change through Ken'sagent_teamtools. Ken applies it when the campaign's Autopilot is on and the change is inside its bounds, and turns it into a proposal otherwise. The agent never uses Ken's direct write tools. - Proposals are approved in Ken. They wait in Today, and only a person in Ken can approve one. The agent can't approve anything.
- On a client workspace, a schedule or volume change needs the client's yes on the proposal before it can be applied.
- The agent acts as you, with your role. Prefer an API key in a request header for a scheduled run, never paste a key into a chat, and switch off Ken's other write tools where your tool allows it.
- Credits. The agent's thinking costs no Ken credits. Ken actions cost what they cost in the app: a lead top-up pays for the emails Ken finds and the AI work that follows.
Run Ken's agent templates in your own AI tool lists what Ken can apply on its own, with each bound and undo window.
Keep campaigns running
Keeps every live campaign stocked with leads and inside healthy sending capacity, runs the weekly test report, and drafts a client update.
- Status: ready.
- Schedule: once a week, Monday at 07:00 in your time zone. Each run covers every specialist, including the client update, so one weekly task is enough. Ken's Templates tab also lists a daily check at 07:00 and a client update on Fridays at 15:00; in your own tool, the Monday run does both.
- Specialists: Lead loader, Capacity, Deliverability guard, Tester, Strategist, Reporter.
- Skill:
keep-campaigns-running
What each specialist does in a run:
| Specialist | Applies, with Autopilot on | Proposes |
|---|---|---|
| Lead loader | When a campaign has fewer days of leads than your target (7 unless you change it), adds leads from its approved audience to cover about a week more than the target | The campaign's audience, until one is approved, and top-ups past the weekly limit or when credits are out |
| Capacity | Moves the daily cap toward what the healthy inboxes can send, within the bounds | Sending days, the sending window, pause and resume |
| Deliverability guard | Takes a sick inbox off the campaign, puts it back once it recovers, and runs a placement test after a copy change or when mail lands in spam | Nothing else. It never takes a campaign's last inbox off, and says so in the summary instead |
| Tester | Makes a test's version the default once Experiments grades the test proven | Nothing. Below proven, it says how far along each test is |
| Strategist | Nothing | New copy for a campaign whose interested replies stall, and new angles for the workspace |
| Reporter | Nothing | On a client workspace, one short update per campaign each week, for you to approve |
With Autopilot off, every change in the middle column becomes a proposal too. If Experiments isn't on for your workspace, the Tester says so and skips its part.
Starter prompt:
Load the Ken skill keep-campaigns-running and run it for this workspace. Change campaigns only through the agent_team operations, and leave everything else as proposals for me to approve in Ken.
At the end of each run, the agent writes a short summary: what changed, with each undo deadline, what it proposed, and what to watch next week.
Coming later
These templates aren't ready yet. They have no skill or starter prompt, and Ken's Templates tab marks them as coming.
| Template | What it does | When it runs | Specialists |
|---|---|---|---|
| Launch a campaign | Builds a campaign from a brief, sends its first batch for review, then hands it to Keep campaigns running | When a person gives a brief | Strategist, Lead loader, Capacity |
| Deliverability rescue | Steps in on a bounce or complaint spike: takes sick inboxes out of rotation and slows the campaign | On a bounce or complaint spike | Deliverability guard, Capacity |
| Angle explorer | Runs 5-10 small campaigns on different angles and shifts volume to the winners | When a person asks | Strategist, Lead loader, Capacity, Tester |
| Signal-fed evergreen | Feeds a campaign leads with a fresh signal, such as funding, hiring or a tech change, with an opener that names it | On a signal for the campaign's audience | Signal scout, Lead loader, Strategist |
| Recycle finished leads | Gives contacts who finished a sequence 90 or more days ago without replying a new angle in a new campaign | Weekly | Lead loader, Strategist |
| Client onboarding | Turns a client intake into a first campaign, with domain and inbox orders a person approves | When a person submits a client intake | Strategist, Lead loader, Capacity, Deliverability guard, Reporter |
Next: Run Ken's agent templates in your own AI tool, What Ken does on its own or How credits work.