Give every answer a useful interface.
Frigade presents answers as tables, record links, and choices inside the conversation, so your users can find what they need and take the next step.
Overview
Keep the information beside the decision.
A weekly schedule is easier to scan as a table. An order is easier to follow up on when its record is one click away. Frigade puts those views in the answer, where your users need them.
When the assistant needs a choice, it can show the available options in the conversation. Your users select an answer and continue with the task.
Make the answer easier to scan.
The same schedule can be a paragraph or a table. A structured view puts the details beside each other, so your users can compare them at a glance.
Read through the details.
Find the detail you need.
| When | Appointment |
|---|---|
| Mon 9 AM | Acme onboarding |
| Tue 2 PM | Beacon review |
| Thu 11 AM | Orbit check-in |
A useful view for each question.
Show information clearly, link to the relevant record, or ask for the choice needed to continue.
“where are my last two orders?”
Order #4821 and Order #4830 are both in transit.
Open the right record
Link to the returned orders so your users can open the record they need.
“send the team the weekly report”
How should I send the report?
Choose how to continue
Offer the available delivery options and use the selection to continue the conversation.
“move Acme to the Pro plan”
Review a proposed change
Show the account and proposed plan together so your users can check the details before approving.
“what's on my calendar this week?”
Scan the schedule
Put appointments in a table so dates and times are easy to compare.
The assistant chooses a view for the answer.
Frigade uses the question and available product information to compose its response. It can format a schedule as a table, link to a returned record, or offer choices when it needs more detail. Skills and tool calls retrieve the data and perform actions.
Make the decision clear.
A confirmation can show the proposed change and its timing together. The Skill or tool handles the action. Use your product's access and approval checks for the action itself.
Put an action behind the answer.
Connect the conversation to enabled Skills or a tool you define. Your users can ask for a result and review it in the same place.