Turn customer requests into completed actions.
Give AI agents defined actions in your business systems. Use assigned platform tools or configured APIs to retrieve information, book appointments and update records.
Talk to salesTool Kit
2 assignedGet Availability
Get the most up-to-date availability from your connected calendar.
“What times are available this week?”
Book Appointment
Book an appointment from an available calendar slot.
“Book that appointment for me.”
Library
Service Availability
Look up service appointment options through your own API.
“Can someone visit on Friday?”
Powering businesses, agencies and franchise operators.
Household-brand logos represent franchise-level deployments.
Check availability. Then book the chosen time.
A useful action connects what the customer requests to the system that can fulfill it, with the right inputs and a result the agent can explain.
Collect the required inputs
The agent asks for the service and preferred day. The tool definition explains when to run and what information the request needs.
Retrieve the live options
The configured availability tool checks the relevant calendar. Its returned slots give the agent concrete options to offer the customer.
Submit the confirmed choice
The booking action sends the selected time and required details. The returned result tells the agent what to confirm or what needs another step.
Put your systems behind the conversation.
Fewer tasks left for someone else
Equip the assistant with supported calendar, contact and task actions so routine requests can progress during the conversation.
Answers based on current information
Use a live lookup for availability or operational records instead of relying on a saved knowledge source for changing facts.
Specialized workflows through APIs
Define the endpoint, method, parameters and authorized connection for business actions beyond the platform tools available to your account.
Be specific about what the agent can do.
A focused tool assignment makes the intended action and its operating boundaries easier to understand.
Scoped access
Assign relevant actions to each assistant. Keep credentials in supported connection settings and enforce authorization at the receiving system.
Validated requests
Define typed inputs and validate them in your API. Design write operations to handle duplicate requests safely.
Usable failure paths
Plan responses for empty, delayed or failed results. Voice and chat have different deadlines; confirm an uncertain write at its destination before retrying.
Product capabilities and architecture
Assistable Tooling gives an AI assistant defined actions in connected systems. Assign platform tools for supported workflows or configure custom API requests with the inputs, authorization and response handling your business requires.
The actions behind a useful agent.
- Assigned platform tools
- Choose available calendar, contact, task and other platform actions for each assistant. Give it a focused set of capabilities for its job.
- Custom API requests
- Define an endpoint, HTTP method, typed parameters, headers and request format for a business API. Explain when the agent should use it.
- Structured inputs and results
- Specify the information an action needs and return a result the agent can interpret, including no match, completion or an unavailable response.
- Reusable tool definitions
- Reuse eligible configurations across deployments, adapting the destination, credentials and account-specific values for each business.
A clear connection between language and systems.
The agent understands the request. A defined tool connects it to the system responsible for the action.
- Instructions establish the purpose
- Tool descriptions explain when to use an action and which details to collect.
- Configuration defines the request
- The endpoint, parameters and authorized connection determine what reaches the receiving system.
- The result shapes the response
- The returned information shapes the agent’s response. Longer work can follow a designed follow-up path.
Operating controls and references
Give access with a defined purpose.
Tools should be as specific as the job the agent is authorized to perform.
- Scoped assignments and credentials
- Assign the relevant actions to each assistant and keep credentials in supported connection settings, outside the conversation.
- Validation at the receiving system
- Your API controls authorization and input validation. For write actions, design duplicate-request handling around the business operation.
- Clear unavailable-result behavior
- Define the customer response when a tool fails or times out. A timeout requires a destination check before repeating an uncertain write.
Tooling
questions.
Do all actions require a custom API?
No. Use the platform tools and integrations available to your account for supported workflows. Custom API tools cover specialized lookups or actions those connections do not provide.
Can tools work in voice and chat?
Supported tools can serve an assigned assistant across eligible channels. Voice and chat have different execution deadlines and presentation, so configure the action and its fallback for each channel.
What happens if a write request times out?
The receiving system may have completed the action even if the response did not arrive. Check its record before repeating the request and design the endpoint to handle duplicates safely.
Can we reuse a tool across client accounts?
Eligible tool definitions can be reused, but endpoints, headers, credentials and identifiers may refer to the original business. Review and update those values before assigning the copied tool to another customer's assistant.
Connect the action your customers came for.
Show us the system and the task. We will help define the tool, required inputs and customer experience around its result.
Talk to sales