BOT_01
Signal Scout
Clusters recurring support issues and preserves source links.
→ hands findings to Pattern Analyst
Keypra TEAM diagnosticHuman approval before the team is drafted
One Bot—ora TEAM?
Send the whole job, even if it feels messy. Keypra separates genuine roles from unnecessary complexity, then shows you the smallest Bot setup that can handle it clearly.
The proposal flow
Diagnosis first. Build only after you agree.
01 / BRIEF
Email the whole workflow
Describe the inputs, decisions, outputs and human approvals in ordinary language. Do not split it into Bots yourself.
02 / JUDGE
Keypra tests one versus many
If one role can own the work cleanly, you get one Bot. If jobs or boundaries conflict, you get a focused 2–4 Bot proposal.
03 / APPROVE
Reply TEAM to build the rest
The first full pack arrives with the proposal. Reply TEAM only if the named roles and handoffs make sense to you.
Example diagnosis
A workflow becomes three clear jobs.
Monitors support tickets, finds recurring product issues, drafts a weekly insight note, and prepares reply suggestions. Nothing is sent or published without human approval.
One Bot would mix evidence gathering, analysis and customer-facing drafting. Three roles make the handoffs inspectable.
BOT_02
Pattern Analyst
Tests the evidence, ranks themes and drafts the weekly insight note.
→ hands approved themes to Reply Drafter
BOT_03
Reply Drafter
Prepares response suggestions from approved themes and policy.
→ hands every draft to a human
What you receive
Separate packs. Explicit handoffs. No mystery agents.
Named roles
Each Bot has one job, a title, and a stopping point.
Day One Instructions
Inputs, outputs, checks, escalation rules and approval boundaries for every role.
Handoff map
Who receives what, from whom, and where human judgement enters the flow.
Paste-ready files
Markdown and Word packs for your own setup, review and versioning.
Small by design
Two to four Bots—or one.
More Bots are not automatically better. Keypra recommends a TEAM only when separate responsibilities improve clarity and control. If the brief needs more than four, we treat that as a process-design problem first.
A split is not a security wall
Bots in one xAI account may share a cloud computer, files, browser sessions and logins. Separate Bots clarify jobs and handoffs; they do not create separate credentials or security boundaries.
You stay in control
Keypra drafts and teaches. It never runs your Bots, connects your xAI account, sends messages, publishes, deletes or spends on your behalf.
Credits stay visible
A team uses roughly one pack's credits per member. The proposal tells you the size first, and no remaining team packs are generated until you reply TEAM.
Consent before storage
EU processing, explicit consent, and STOP at any time.
Made by Keypra
The human layer for AI at work—built for people who inspect the handoff.
Operated by
Keypra OÜ
Sepapaja tn 6, 15551 Tallinn, Estonia
Registry code 17502390
Human support
hello@keypra.com