Build the bots your GTM team needs. Running the flows you want, pointed at revenue.
Bonggy is the agent workspace for sales, RevOps and marketing teams. Describe the work in a sentence; a bot turns it into a flow tied to a revenue goal, and you approve what customers see.
Demo: you type “when a lost deal's champion changes jobs, tell me and draft a note.” The bot names itself Boomerang and fills its flow: trigger, context, steps, approval (you, before any note is sent), output and goal (q4 new pipeline). Next morning it finds a champion who moved to a new company, drafts a note, and waits. You approve it. Its receipt: matched 1 champion, drafted 1 note, added 1 crm task; sent after your ok, nothing else sent.
One workspace. Three teams.
Sales, RevOps and marketing teams each build bots for their own work. Every bot answers to a revenue goal.
Sales
A brief before every call, and a next step on every deal.
RevOps
A clean pipeline and a forecast you can explain.
Marketing
Messaging built from what customers actually say, and leads that reach the right rep.
Every bot runs a flow you design.
Six parts: trigger, context, steps, approval, output and goal. Change any of them, any time.
Start from a preset, or from a sentence. Either way, the flow is yours.
Demo: the Unstick flow, with six parts. Trigger: every Monday at 08:00. Context: open deals in the crm, calendar and call notes. Steps: read every open deal, flag deals with no next step or 14+ days quiet, suggest one next step per deal. Approval: you, before any crm change, with a hard limit: never email anyone. Output: this chat and a crm task per deal. Goal: q4 enterprise logos. You change the trigger to Fridays after forecast and narrow the context to enterprise deals. The run reads 18 open deals, finds 5 stuck, adds 5 next-step tasks, and sends nothing.
Flows teams have built
A bot for every job.
Say what you want in plain words, and what it must never do. The limit becomes part of the flow.
Unstick. Flags stuck deals every Monday. Never emails anyone.
- You said
- “Every Monday, flag my stuck deals. Never email anyone.”
- Hard limit
- never email anyone
- Flow
- mondays 08:00 · internal only
Your process, not ours.
Demo: you tell Unstick “Every Monday, flag my stuck deals. Never email anyone.” The flow saves as mondays 08:00 · internal only, with the hard limit “Never email anyone.” The bot reports: 5 of 18 open deals are stuck: 3 have no next step, 2 went quiet 14+ days. You approve. It confirms: added 5 next-step tasks to your crm. nothing sent.
Make it yours.
Pick a colour, a shape and a face. Your bots look like yours everywhere they show up.
Colour
Shape
Eyes
Accessory
Boomerang
salesSpots when a past champion lands at a new company and drafts the reopen.
Bots hand off work.
Put bots from different teams in one group. Marketing's research reaches sales without anyone copying it across.
Demo: a group called Marketing → Sales handoff with three bots: Echo, Unstick and Relay. Echo posts the top pains from 24 calls (slow onboarding, manual quotes, no forecast view) and hands them to Unstick. Unstick adds the matching pain to each stuck deal's next-step note and sends nothing.
Bots draft. You decide.
Anything a customer would see waits for a person. Everything else can run on its own, if your team says so.
Demo: the approvals inbox. Boomerang wants to send a note to Dana at Globex and needs your ok. Unstick wants to add 5 next-step tasks to your crm. Relay briefed 4 reps in #inbound, done and internal only. Echo's post to #q4-campaign is held for you. You open the note to Dana, read it, and approve it.
Approval by action. Anything customer-facing (emails, posts, sequencer pushes, published content) needs a person. Internal output (a brief in chat, a Slack summary) can run without approval if your team chooses.
No volume blasting. Marketing bots draft and research; they don't mass-send. Campaign sends stay in your own tools, after approval.
No leaderboards. Work is measured against revenue, never person against person.
Humans stay in charge. Bots work only through the tools and permissions you connect.
See what every bot did, and why.
Runs, approvals and the revenue goal behind each one. Filter by team.
- Boomerangsales
- runs
- 14
- approved
- 1
- est. hours
- 0.5
q4 new pipeline - Unsticksales
- runs
- 4
- approved
- 4
- est. hours
- 3
q4 enterprise logos - Compassrevops
- runs
- 30
- approved
- 2
- est. hours
- 4.5
q4 enterprise logos - Echomarketing
- runs
- 3
- approved
- 1
- est. hours
- 2
pipeline from inbound - Relaymarketing
- runs
- 21
- approved
- 19
- est. hours
- 3.5
pipeline from inbound Total · all
- runs
- 72
- approved
- 27
- est. hours
- 13.5
demo data
What bots read
Each fact a bot uses links back to where it came from. Read-only unless a flow says otherwise.
- crm notes212 · 2h ago
- call notes64 · 1h ago
- docs9 · 3d ago
Your context, read first.
Company defaults every bot starts from, with overrides where a team works differently.
Company context
read first by every bot
- ICP
- b2b saas, 50–500 employeesrevopsoverrides company defaultenterprise plan: 1000+
- Tone
- plain, specific, one clear askmarketingoverrides company defaultwarmer, story-first, still no hype
- Deal stages
- discovery → evaluation → proposal → closed
- Never
- never contact current customers' champions without the AE
Every flow runs on one loop.
Track
Bots read activity across the tools you connect.
Align
Every action maps to a revenue goal.
Nudge
Drift gets flagged with a suggested next step. A person decides.
Report
One view of work against goals, from rep to CRO. No leaderboards.
Pay for the bots you run. Plus what they use.
Pricing is based on active bots plus usage. Flow runs count toward usage. We're setting plans with our first teams, so there are no public numbers yet.
Included
- Bots for sales, RevOps and marketing
- Flows with all six parts
- Approvals inbox
- Analytics
- Company context with team overrides
Questions, answered.
See all questionsGive your first bot a purpose.
Start from a preset, or from a sentence. Either way, the flow is yours.