Solutions

Daily operations

The handbook answer, with the page named.

#people-opsprivate channel1 tool call

A policy question answered only from the documents you indexed, with the document and the heading it came from. “Check our docs” forces the search; a document scoped to one channel is not answerable from another.

people-ops

Priya4:07 PM

@attest_tag what's our policy on carrying leave into next year? check our docs

attest_tagApp4:07 PM

  • search_docs · “carry leave next year” · 4 chunks

Up to 5 days carry into Q1 and expire on 31 March. Anything above 5 needs your manager’s sign-off before 15 December, and contractors are out of scope entirely.

  • Employee handbook — §4.2 Annual leave
  • 2026 policy update — Carry-over changes

google/gemini-flash3.9k in220 out$0.0021Configure

Names, figures, repositories and customers are changed; token counts and cost are illustrative. The ask, and the shape of the answer, are as they were.

How the turn went

Indexed, searched on demand, cited by document and heading.

  1. 01

    Indexing

    A folder, a bucket, or a shared Drive folder mirrored in. Documents are chunked at about 500 tokens, each chunk keeping its nearest heading, embedded and stored. Indexing runs on start, every six hours, on !ingest, and from the console.

  2. 02

    The forced search

    “Check our docs” must call search_docs and answer only from what comes back. Nothing found is “nothing found”, not a general-knowledge answer dressed as policy.

  3. 03

    The citation

    The document and the heading, so “answered from the handbook” is checkable rather than a claim.

What it needs

The setup, in the console.

Documents
Files in the documents folder or bucket, or a shared Drive folder synced by a service account. Plain-text documents can be edited in the console.
Scope
A document can be limited to one channel, so the support handbook is not answerable from engineering.
Embeddings
An embedding model from the same provider as the chat model, or another endpoint, set in the console.

What it will not do

Enforced outside the model.

  • It will not answer a “check our docs” question from anything but the index.

  • The Drive service account sees only folders shared with its own address, never everything on the domain.

Try it

Say it in a channel it is in.

The sentence as it was typed. It works in any channel the bot has been invited to that carries the connection above — no command syntax, no form, and follow-ups in the thread need no mention.

@attest_tag what's our policy on carrying leave into next year? check our docs

  • Google Drive
  • search_docs

Bring the channel this would live in.

Sign up, connect the service above in one channel, and type this sentence yourself — or run the same binary on your own infrastructure.

All solutions