# Bonggy: the agent workspace for sales, RevOps and marketing > Sales, RevOps and marketing teams build bots from a sentence. Each bot runs a flow tied to a revenue goal. Bots draft; people approve what customers see. Source: https://www.bonggy.com ## What Bonggy is Bonggy is the agent workspace for sales, RevOps and marketing teams. Teams build bots from a sentence; each bot runs a six-part flow tied to a revenue goal, and a person approves anything customers see. **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. ## One workspace. Three teams. Sales, RevOps and marketing teams each build bots for their own work. Every bot answers to a revenue goal. **Sales** - **Boomerang** — Tells you when a lost deal's champion changes jobs. Spots when a past champion lands at a new company and drafts the reopen. - **Dossier** — A brief before every first call. Digs into an account and its people so the rep walks in prepared. - **Unstick** — Mondays: stuck deals and next steps. Finds stalled deals and suggests the next step that moves them. - **Draftsmith** — Research into a follow-up draft, for approval. Turns research into a brief or message a rep can actually use. **RevOps** - **Compass** — Accounts drifting from the ICP, deals with no next step. Watches the pipeline against the goal and nudges when it drifts. - **Tidy** — Missing fields and duplicates; proposes fixes, for approval. Cleans up CRM records, fills gaps and flags what's off. - **Delta** — Before the weekly call: what changed and why. Preps the forecast and explains what changed since last week. **Marketing** - **Sweet Spot** — Segments and which ones win. Maps the segments most worth your team's time. - **Echo** — Pains and objections from recent calls. Pulls themes and pains out of calls and campaigns. - **Quill** — Posts, pages and emails in your voice, for approval. Drafts content in your team's voice, ready for review. - **Relay** — Scores new leads against the ICP and briefs the right rep. Routes inbound leads to the right owner, fast. ## Every bot runs a flow you design. Six parts: trigger, context, steps, approval, output and goal. Change any of them, any time. - **Trigger** — when it runs - **Context** — what it reads - **Steps** — what it does, in order - **Approval** — who approves what, before which action - **Output** — where the work lands - **Goal** — the revenue goal it answers to Start from a preset, or from a sentence. Either way, the flow is yours. ## Bots hand off work. Put bots from different teams in one group. Marketing's research reaches sales without anyone copying it across. ## Approvals - **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. Every run leaves a receipt: what the bot read, what it did, who approved it, and what it didn't send. ## See what every bot did, and why. Runs, approvals and the revenue goal behind each one. Filter by team. ## Your context, read first. Company defaults every bot starts from, with overrides where a team works differently. Bots connect to the tools your team already uses: CRM, email, calendar, Slack and call notes, through the permissions you connect. ## The 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. ## Pricing 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. ## FAQ **What is a bot?** A bot does one job for your team, like researching accounts before calls. You describe the job in a sentence and it runs as a flow. **What's in a flow?** Six parts: trigger, context, steps, approval, output and goal. Every part stays editable. **What's a hard limit?** A rule in your own words, like "never email anyone". It becomes part of the flow, and the bot can't cross it. **What can bots do without approval?** Only internal work (briefs in chat, Slack summaries, reports) and only if your team allows it. Nothing customer-facing goes out without a person approving it. **Do marketing bots send campaigns?** No. They research and draft. Campaign sends stay in your own tools, after approval. **Which tools does it connect to?** The ones your team already uses: CRM, email, calendar, Slack and call notes. Bots only use the permissions you connect. **How is my data handled?** Bots are built to be read-only by default and write back only where a flow your team sets up allows it. Bonggy is built for encryption in transit and at rest, there's no training on your data, and you can ask us to delete your data at any time. SOC 2 Type II: on the path, not attained. **Who is it for?** Sales, RevOps and marketing teams. It usually starts with one team's flows and spreads as other teams build their own. **How is it priced?** 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. **How do we start?** A strategy call. We'll map one flow with you on real work. ## How to start Book a strategy call and we'll map your first flow with you on real work. - Strategy call: https://cal.com/bonggy/30min - Email: founders@bonggy.com Bots draft. People approve.