Beside existing systems
Keep mail—and delivery—where they are
Gmail or Microsoft 365 remains the communication channel, and approved work can be created in monday.com. Bondi owns classification, routing and the exception path between them.
For the shared mailbox that became an unofficial queue
Turn incoming client requests into work with an owner.
Connect Gmail or Microsoft 365, then decide where delivery runs. Bondi can route the request into monday.com or into a complete client-operations system built in Bondi. The message that fits nothing becomes an owned exception instead of remaining unread.
From event to outcome
Follow the work through its human decision.
A mailbox event starts the workflow. Classification returns one of the categories your operation defined, then Bondi looks up the account and routes the request to its working record. That record can live in a connected delivery tool or in Bondi. The default and sensitive branches suspend for a person with the original message attached, so the inbox remains the communication channel while the work becomes accountable.
Illustrative workflow
Owner required - Gmail or Microsoft 365 Incoming client message Built-in connector
- Bondi Classification, account match and exception Bondi runtime
- monday.com or Bondi The delivery work itself Built-in connector
- 01 Receive the mailbox event integrationTrigger · Gmail / Microsoft 365
- 02 Classify it into your categories classifyText · named operational categories
- 03 Match the client and current engagement bondiDataLookup · account + engagement
- 04 Give unclear or sensitive requests to an owner interactiveForm · message attached
- 05 Open the work where delivery runs monday.com action or bondiDataCreate
Configured human task
Service owner
Anything that matches no category, or a category you marked sensitive, waits for an ownerContext shown
The original request, proposed category and any sensitive or unmatched details.- Confirm category and owner
- Request more information
sample_ops / automations / client-request-routing Illustrative execution
Run inspector
Request · access change for Sample account
The classifier returned the explicit review category, so the request cannot enter delivery without an owner.
- Mailbox
- Microsoft 365 · support@
- Category
- Access or permission change
- Current step
- Assign and confirm request
- Destination
- monday.com · Client delivery
If nobody responds
The request remains visible in the exception queue and escalates to the service lead.
Where the records live
Run the process beside your tools or within Bondi.
Keep one authoritative home for each business record. Choose the boundary that fits the process you are building.
Connection requirements
Set up the connections this example uses.
This is a worked example of a configurable workflow. Connections and decision rules must be set up for your system.
Explore integrationsGmail or Microsoft 365
A signed provider event starts the workflow when the message arrives.
monday.com or Bondi
monday.com is a built-in connector; a Bondi record needs no external connection.
The wider operation
See the system around this workflow.
Explore the records, screens and other decisions that can stay connected to this process.
Start with your process
Describe one handoff you want to improve.
Name the starting event, the records involved and the decision that needs a person. Review the plan before building the workflow.
No credit card required.