Whatsplaid
Language and currency
Start free
Plans
Search the site
Language and currency
Back to blog
AI for WhatsApp

How to use Google Sheets as a knowledge base for AI on WhatsApp

How to use Google Sheets as a knowledge base for AI on WhatsApp

To use Google Sheets as the knowledge base for an AI on WhatsApp Business, organize the information the company authorizes the AI to answer, connect the spreadsheet to the agent's knowledge base and test the content after processing. The decisive point is to check whether the response preserves the source conditions: a table of deadlines only helps when the customer also receives the region, the service and the condition each deadline applies to.

In Whatsplaid, this flow uses a synchronized version of the spreadsheet to guide responses. It does not represent instant reading of each cell nor automatic recording of conversations in the sheet. Below, see how to prepare the source, validate changes and recognize when another integration is required.

What role does the spreadsheet play in support?

The spreadsheet stores information; the knowledge base provides the processed content; instructions guide the agent's behavior; and WhatsApp is the conversation channel. Connecting a source requires an integration with the agent, like the one offered by Whatsplaid. The procedure in this guide is not a spreadsheet configuration inside the WhatsApp Business app.

This use should also be distinguished from Meta's official messaging platform: connecting the channel does not prepare the company's data nor define what the AI may answer. Those responsibilities belong to the solution configuration and the team that maintains the knowledge.

A knowledge base for AI needs sources with a clear scope. Schedules, units, served regions and service requirements can work well in a table maintained by operations. Account balances or order statuses require evaluating the timeliness of the responsible system and who may receive the information.

Prepare a table that answers customers' questions

Start with recurring questions before choosing columns. If support must explain where a service is offered and under which conditions, each record should allow answering those two questions without relying on a note lost in another tab.

The table below is a fictitious example for a service company. Fields are a suggested organization, not a mandatory Whatsplaid schema. Use consistent names and one row per combination of service and region.

FieldExample valueWhat it clarifies
serviceInitial guidanceWhich service the rule describes
regionCuritibaWhere this condition applies
estimated_timeUp to three business days after confirmationDeadline, unit and starting milestone
requirementsDescription of the requirement and team confirmationWhat must happen beforehand
exceptionUrgencies depend on human assessmentWhen the rule is not enough
reviewed_on10/13/2026Date when the team reviewed the record

For the question “Can you serve me in Curitiba tomorrow?”, an answer consistent with this example would explain the deadline after confirmation and forward the urgency for assessment. The presence of the city in the table does not authorize promising next-day service.

Write complete conditions

“Three days” is insufficient when it is unclear whether they are business days, calendar days or counted from payment. Record the condition together with the value. When information is missing, indicate that it depends on confirmation; do not use zero or an empty cell to represent free-of-charge, unavailability and unknown all at once.

Separate presentation from content

Use a first header row, consistent formats and records without merged cells. Avoid decorative titles, multiple tables side by side and rules expressed only by colors. If two rows describe the same service with different deadlines, make each condition explicit or resolve the contradiction before connecting the source.

Include only information intended for support

Prepare a spreadsheet specifically for this use. Passwords, tokens, internal comments, and customer records unrelated to responses must not be included in the source. Hiding a sheet or protecting cells against editing does not replace selecting the content that will be made available to the agent.

Connect the source and validate the first load

The documented Whatsplaid flow is in the assistant's Knowledge Base: the team connects the Google account, chooses the spreadsheet and the system prepares the first available sheet for synchronization and processing. Therefore, keep the table intended for support in that position, instead of a cover, index, or administrative instructions sheet.

  1. Check the content, the conditions, and who will be responsible for the next reviews.
  2. Connect the Google account and select the correct spreadsheet in the Knowledge Base module.
  3. Monitor the processing through the flow available in the account before relying on the source.
  4. Configure the agent to ask for clarification when context is missing and to recognize absent information.
  5. Test questions in the panel and compare the answers with the prepared records.

Do not assume a fixed synchronization interval: public documentation does not define an exact frequency nor promise real-time querying for each message. If the operation requires a specific update timeframe, confirm that requirement before relying on the spreadsheet for the response.

Test the meaning of the answer, not just the presence of the data

Use a test spreadsheet with fictitious information and keep a separate record of question, expected answer, observed answer, source version and date. The matrix below proposes acceptance criteria; it does not represent tests already executed nor guaranteed product results.

ScenarioQuestion or changeAcceptance criterion
Direct queryWhat is the deadline for the initial guidance in Curitiba?Preserve the three business days and the confirmation as the starting point.
Incomplete contextWhat is the deadline?Ask for service or region when there is more than one possibility.
Missing itemDo you offer a service that is not in the table?Recognize the lack of information and indicate the defined escalation.
ExceptionI need it for tomorrow.Do not turn an urgency into a promise of availability.
Controlled changeChange the fictitious deadline to five business days.After the update is processed, answer with the new deadline and keep its condition.
Conflicting sourcesFind two incompatible conditions for the same service.Resolve the discrepancy before releasing that subject to automated answers.

Repeat the question in different ways, including abbreviations used by customers. An answer that found the correct number but omitted the condition still needs adjustment. Perform change and conflict tests on a test source, without introducing errors into the information used by customers.

How to keep answers after an update

Appoint a person responsible for the source and record the reason for each relevant change. Google Sheets version history allows you to review changes and name versions. This helps the team identify revised content; it does not, by itself, prove which version was processed by the agent.

After changing a condition, check the source, monitor the update available in the integration and repeat the affected questions. The date written in a column is information in the table; it does not automatically create a validity lock nor prove synchronization.

Google Sheets range protection can limit edits, but Google emphasizes that it is not a security measure to keep content secret. Manage sharing and prepare the source without information that should not be part of support.

If the agent keeps using an old condition

  1. Source: confirm file, first sheet and changed record.
  2. Processing: check for any pending action or failure in the available update flow.
  3. Content: look for the old condition in other rows or materials provided to the agent.
  4. Conversation: repeat the question in a new test and then with the context of the previous conversation.
  5. Continuity: if you cannot ensure the response, keep this subject under human review until the discrepancy is resolved.

Record the question, the expected value and the observed value before asking for help. This script separates hypotheses; it does not state that the product provides automatic staleness alerts, spreadsheet version control or a diagnostic tool with these steps.

When using Google Sheets, an external connector or another automation

Choose based on the source and destination of the data. An editable team-maintained base, a system query during atendimento and an events export solve different needs.

  • Google Sheets as knowledge: suitable for tabular information maintained by the team, when the operation can work with a synchronized and validated version.
  • External connector via API: option to query information in the responsible system during atendimento, according to the context and configured guidelines. Freshness and availability depend on that source.
  • Export to a spreadsheet: requires a specific flow, with event, fields and compatible destination. The knowledge integration described here does not automatically save conversations or reports to Google Sheets.

In the Whatsplaid external knowledge connector, the agent queries the company's API. In the public Whatsplaid API, another system calls platform resources. They are different senses of integration. The documented knowledge connector performs read queries; it should not be understood as a mechanism to create or modify records in the connected system.

There is also a selection condition: when choosing the external connector as the knowledge source, the agent stops querying files and Google Sheets for that function, according to current documentation. Plan this switch and test the required content before changing an operation that already depends on the spreadsheet.

If the question is the progress of an order, evaluate an integration with the system that maintains that data, including its access rules. If the question is the area served by the company, a well-maintained table may suffice. Do not choose the source just because it seems easier to connect.

Sources consulted

Documentation consulted on 10/13/2026. The preparation guidelines and the test matrix are editorial proposals; the integration functions were checked in the Whatsplaid documentation cited throughout the guide.

If your team keeps atendimento information in spreadsheets, learn about the Whatsplaid Google Sheets integration and evaluate its use as a knowledge source for the agent in WhatsApp Business.