Find the relevant information
Use enabled tools to consult the record that matters to the request, with the account access and customer identity checks the workflow requires.
Apps and integrations
Your customer has a question. Your team has information spread across email, calendars, customer records, orders, and support tools. Office 168/52 brings those pieces into Bob's front-office workflows so a conversation can lead to a useful answer, a prepared action, or a clear handoff.
Bob reads the record the conversation needs, takes the next approved action, and keeps your team in the handoff. You choose which steps require approval.
50 integrations
Let's find another way to connect your workflow Try another app name or tell us which system your team uses and what you want Bob to help with. Request an integration
An integration gives a workflow a defined way to retrieve information or take an approved action. That might mean finding the right customer record, checking an appointment, preparing a support ticket, or sending a reviewed follow-up. Bob uses the result to help the conversation move forward.
Use enabled tools to consult the record that matters to the request, with the account access and customer identity checks the workflow requires.
Turn the customer's request into structured details for a reply, task, booking, or handoff, instead of making someone start intake again.
Your business chooses which actions are enabled, when approval is required, and where exceptions should go.
Example workflows
Each example shows how the apps work together on one customer job. Your team chooses the connections and the approval steps.
Bob collects the prospect's need on a WordPress site, prepares the appropriate HubSpot handoff, and helps the customer reach the right Calendly booking. Each connection contributes a specific part of the process.
An authorized Shopify lookup can provide order context, while a configured Gorgias workflow gives the service team the customer's request and the details needed for review.
Bob captures the purpose of an enabled business call, prepares the field-service intake, and routes the follow-up to the team's chosen communication workflow.
Tell us the app and the job you want Bob to help with. A useful request starts with the outcome: look up a service status, collect a lead, check an order, or prepare the next handoff. We'll use those details to discuss the right connection path.
Include the app name and the workflow you have in mind. Keep passwords and API keys out of the message.
A connection makes specific tools available to a configured workflow. Your account permissions, provider access, and enabled Office 168/52 tools determine what Bob can read or do.
These workflows are designed around your existing systems. Bob helps with the conversation, intake, and next step while your team keeps its established business tools.
No. Some services use a supported authorization flow, while others need a plugin, API credentials, provider eligibility, or guided setup. Each detail page explains the intended connection path.
Yes. Start with the customer task that matters most, then add the connections that make that workflow more useful.
Choose an integration, explore the workflow, and tell us how your front office handles that job today.