Write instructions once, reuse them everywhere
Use owned content to answer visitor questions with less friction.
7-day free trial
What this feature covers
Why it matters
The practical reason to use it.
Teams running more than one assistant usually end up rewriting the same instructions each time: the same tone guidance, the same policy wording, the same task prompts, just pasted into a new.
How it works
A step-by-step look at the workflow.
Step 1
Write and save a prompt template, such as a tone guide, a policy answer, or instructions for a recurring task.
Step 2
Organize templates by purpose so tone guidance, policy wording, and task prompts are easy to find later.
Step 3
Attach a saved prompt to a new or existing assistant instead of writing instructions from scratch.
Step 4
Update the template when tone or policy changes, then reapply it to the assistants that use it so answers stay consistent.
Core job
The main job this feature handles.
Saved prompt templates
Store instructions, tone guides, and task prompts once so they're ready to reuse.
Organized by purpose
Group templates by tone, policy, task, or use case so the right prompt is easy to find.
Apply to any assistant
Attach a saved prompt to a new or existing assistant instead of writing instructions from scratch.
Update once, reapply everywhere
Improve a template in one place, then reapply it wherever it's used.
Daily use
How teams use it after launch.
Consistent brand voice
Keep tone and phrasing aligned across every assistant your team launches.
Policy-safe answers
Save the exact wording legal, support, or compliance already approved for sensitive topics.
Shared across the team
Give teammates a starting point instead of asking everyone to write instructions independently.
Faster assistant setup
Launch a new assistant in minutes by starting from an existing, proven template.
Control points
What to keep controlled.
Multi-assistant rollout
Standardize instructions across every website, client, or department assistant you manage.
Fewer inconsistencies
Reduce the chance that one assistant answers a policy question differently from another.
Proven starting points
Reuse instructions that already tested well instead of guessing at wording again.
Common task templates
Save prompts for recurring tasks like summarizing, qualifying, or routing so they don't need to be rebuilt.
What you get
The changes teams should notice first.
- Faster setup for every new assistant
- More consistent tone and policy answers across the board
- Less time spent rewriting the same instructions
- Easier updates when one change should apply everywhere
The facts do the selling
Plan facts, platform capabilities, and worked examples — every claim here is checkable, not a pitch.
White-label included — never a paid add-on. Copyright removal from $98/mo. Full white-label — custom domain, branded portal, your-domain emails — from $198/mo.
The white-label wedge
Platform fact
Training runs on your sitemap, PDFs, docs, and YouTube transcripts. Answers cite the source pages they came from.
Trained on your content
Platform fact
Five clients at $300/mo on a $198/mo Agency plan is $1,300+ of monthly margin before usage.
A 5-client agency on one flat plan
Worked example
Your questions, answered.
Tap any question about the product, pricing, security, or setup to see a straight answer.
InsertChat
Answers about InsertChat
Hi! Tap any question below and I'll answer it for you.
Prompt Library questions
What goes into a saved prompt?
Tone guides, policy wording, FAQ answers, and instructions for recurring tasks all work well as saved templates. The goal is anything you'd otherwise retype for every new assistant. The operational question is whether prompt library makes the workflow clearer once real conversations, real ownership, and real edge cases show up. That is the bar teams should use before they expand the rollout across more assistants, more channels, or more teams.
Can I update a template after assistants are already using it?
Yes. Edit the saved template when tone or policy changes, then reapply it to the assistants that use it so wording stays current without editing each one by hand. The operational question is whether prompt library makes the workflow clearer once real conversations, real ownership, and real edge cases show up. That is the bar teams should use before they expand the rollout across more assistants, more channels, or more teams.
When is a shared library overkill?
If you only run one assistant with simple, one-off instructions, a shared library may add more structure than you need. It matters most once you're maintaining several assistants that should sound and behave the same way. The operational question is whether prompt library makes the workflow clearer once real conversations, real ownership, and real edge cases show up. That is the bar teams should use before they expand the rollout across more assistants, more channels, or more teams.
Ready to get started?
Start your 7-day free trial. Review current trial terms.
7-day free trial