Connect product, pricing, inventory, or policy tables; choose the response rules;
and add a widget that answers from the rows FrontierBase retrieves.
Connect a spreadsheet, set response rules, and deploy a widget. Every reply points back to retrieved rows and the policy you chose.
Turn the same product, pricing, and policy answers into customer support that keeps working when you are offline.
Give your team chat or API access over Excel, CSV, and Google Sheets, with retrieved rows close enough to review before acting.
Each answer shows the source rows and the response rule it followed (tone, evidence, and safety) through a widget or REST API.
Connect Excel, CSV, or Google Sheets, set rules, then serve answers through a widget or API
Excel / CSV
products.xlsx
Google Sheets
docs.google.com/…
Upload file · Connect Sheets
Step 1
Import products, prices, inventory, and policies from Excel/CSV files or Google Sheets. Everything stays in its original table format, ready to retrieve by row.
Step 2
Choose tone, evidence presentation, and safety rules. These policies are enforced on every generated answer.
Assistant · Just now
Thanks for visiting. How can I help?
Assistant
Latest listed price is ₩1,290,000 (2025-12-01).
Retrieved rows · P001
Step 3
Semantic and keyword search surface the rows that matter. The answer, those rows, and the active response rule are served via widget or REST API.
Every reply stays within the table rows that were found and the response rules you set.
Connect structured data such as products, prices, inventory, and policies directly through Excel, CSV, or Google Sheets.
Answers use only the rows FrontierBase finds for the question, not a summary of the whole document.
When a field is missing from the retrieved rows, the reply leaves it out instead of inventing a value you can inspect later.
Deploy through a web widget or REST API, with conversation context and policies applied consistently.
Previous requests and judgment criteria stay in context so follow-ups do not require re-explaining the same table.
Tone, evidence display, and safety rules are applied to each reply so you can point back to the policy in force.
Serve answers through a web widget or REST API without a heavy custom build.
Repetitive customer support first. The same tables can also cover internal lookup.
Connect product, pricing, inventory, or policy spreadsheets and answer repeated customer questions through a widget—even when you are offline.
Give your team a chat or API interface over Excel, CSV, and Google Sheets, with the retrieved rows kept close enough to review before acting.
What usually changes after you connect tables, set rules, and add a widget.
Outcomes depend on your data and workflows.
After your tables and rules are ready, choose a layout for the chatbot widget.
Tip
A floating button appears in the bottom-right corner. Clicking the button opens the chat panel without disrupting the user's flow. Best for content-first environments such as general websites and landing pages.
Tip
Chat is shown as an overlay covering the entire screen. Other elements are minimized so the user can focus on chat. Ideal for support, onboarding, or focused conversation experiences.
Tip
The main content area is pushed to one side and the chat panel is fixed beside it. Particularly useful when explaining or guiding based on what the user is viewing. Optimized for desktop as an assistant layout: document reading, service guides, admin screen explanations, and similar use cases.
Connect a sample table, set response rules, and try a widget reply from your rows
We use cookies to improve your experience and for marketing. Read our cookie policy or manage cookies .