Bonofici
Menu
Workflows · Playbooks and agents

Watch it done once. Run it every time.

Bonofici learns from your team’s real work and turns it into playbooks agents can run. Your experts stop being the bottleneck.

No integrationsNothing to prepare

The problem

Every company runs on people who just know how things work.

Each rule is worth more than the software it runs on. None of it is written down, and when they leave, it leaves with them.

  • The refund that doesn’t fit the policy

    “Double charges get the duplicate back the same day, no approval. Anything else over $500 goes to finance first.”

    Known by Maya, support lead · 6 years

    Written down anywhere

  • Which customer gets a call

    “If Northwind’s usage drops two weeks running, call before the renewal email. They have left once already.”

    Known by Dev, account manager · 4 years

    Written down anywhere

  • Which spreadsheet is actually right

    “The forecast is “Forecast v3 FINAL (2)”, not the one in the shared drive. The other is last year’s.”

    Known by Priya, finance lead · 8 years

    Written down anywhere

The same gap, in your agents

Your agents know the internet, not how your best people work.

Ask a capable model whether to approve a $900 refund and it will give you a sensible answer. It just won’t be your answer.

Models get better every quarter, for everyone at once. Your playbook is the part that only gets better for you.

A customer wants a $900 refund. Can I approve it?

A general-purpose agent

Most companies allow refunds within 30 days. Check your refund policy and, if the request qualifies, issue it from your payment provider.

An agent with your playbook

Not on your own. Over $500 needs finance approval: post it in #refund-approval and set the ticket to Pending. If it’s a double charge, refund the duplicate now.

Source: “Handle a refund request”, learned from 6 of Maya’s tickets

How it works

Watch. Write it down. Hand it off.

Your team does the work once. Bonofici turns it into playbooks people can read and agents can run.

  1. Watch

    It learns from the apps your team already uses. A few short calls fill the gaps.

  2. Write it down

    Every step, approval and exception, with the work it came from.

  3. Hand it off

    Agents follow it. Anything new goes to a person, and their answer is added.

No integrationsGmailSlackZendeskIntercomHubSpotSalesforceGoogle DriveNotionJiraXeroQuickBooksSAP
Nothing to prepare

No process docs. The work is the documentation, and the people it learns from review what it wrote.

● Playbook · SupportSeen 41 times

Handle a refund request

  1. 1ZendeskRead the request, find the account41
  2. 2SCheck the plan and the charge41
  3. 3SlackOver $500: ask finance, then wait6
    Learned from
    • Slack#refund-approval, Oct 3
    • ZendeskTicket #48213
    • Sch_3Pq…
    • +3 more
  4. 4SRefund in Stripe35
  5. 5Google DriveLog it in the Support Log41
  6. 6GmailReply with the timeline41
Learned from Maya, Tom and Ines
Playbooks with sources

The way your best people work, in a form you can check.

  • Every step links to the tickets, threads and records it was learned from, so you can check it before you trust it.

Where it starts

Playbooks and agents for every desk.

With the playbook, a new hire or an agent handles the cases that used to need your most senior person. We start with what the team does most.

  • Zendesk

    Support

    Which cases need approval, who owns what, when to escalate.

    • Handle a refund request
    • Route a data-deletion request
  • Xero

    Finance

    The vendor paid on the 3rd, the variance that needs a note, the close checklist.

    • Approve the supplier run
    • Chase an invoice missing its PO
  • HubSpot

    Revenue

    Discount rules, approvals, and what was promised on which call.

    • Get sign-off on a discount
    • Hand over an account
  • Google Drive

    Operations

    The workarounds that keep orders, onboarding and vendors moving.

    • Onboard a new supplier
    • Fix an order stuck in fulfilment
Questions

Before you start

What teams ask before they let Bonofici watch the work.

Do we have to write anything?

No. Bonofici learns from the work your team already does, plus a few short calls. The people it learns from can review and correct what it wrote.

Do we need to connect our systems?

No. It learns from the apps as people use them, so it works with the tools you have today, including the old ones with no API.

What if two people do it differently?

The playbook keeps both ways and records when each one applies. You decide which becomes the standard.

When does an agent start doing the work?

Only when you say so, and only for the playbooks you choose. Anything a playbook doesn’t cover goes to a person, and their answer is added to it.

Someone just resigned. Is it too late?

Not if you start now. A few weeks of their real work becomes playbooks the next person, or an agent, can pick up.

No integrations. Nothing to prepare.

Watch it done once. Run it every time.

A 30-minute demo, built around one of your own workflows. Bring the one only a single person knows how to do.