Skip to main content

Setting Up Your Knowledge Base for Cora

Updated over 7 months ago

To act like a true digital teammate, Cora needs to understand your business, your product, and your customers. This starts with a shared knowledge baseβ€”so Cora can answer questions accurately and know when to escalate.

Follow these simple steps to get started:


βœ… Step 1: Open the Cora Knowledge Base Template

Open the Cora Knowledge Base Google Sheet Template (link here)

β†’ Click File > Make a Copy to create your own editable version.


πŸ—‚οΈ Step 2: Fill Out the Two Tabs

πŸ”Ή Tab 1: Common Questions

List 10–20 sample questions that buyers or admins frequently ask.

Examples:

  • β€œHow do I add a new user?”
    ​

  • β€œWhere can I find my invoices?”
    ​

  • β€œWhat are the integration steps for Salesforce?”
    ​


πŸ”Ή Tab 2: Knowledge Resources

Add links to your official help center, internal wiki, onboarding guides, and any other existing resources Cora should use.

Include:

  • πŸ“˜ Help Center (e.g. Zendesk, Intercom, or Notion)
    ​

  • πŸ§ͺ Technical Docs or API Reference
    ​

  • πŸš€ Onboarding Playbooks
    ​

  • πŸ“Ή Training Videos
    ​

  • πŸ“‚ Internal enablement docs (if sharable)

Note: Please flag if any of these resources are gated behind a login wall.


πŸ“€ Step 3: Share with Cora

Once you've filled out the template:

  • Share it in your dedicated Slack channel (where Cora is present), or
    ​

  • Send it via email and CC [email protected]


πŸ” What Happens Next

Cora will:

  1. Ingest your resources and link them to relevant intents.
    ​

  2. Automatically evaluate your sample questions and identify gaps in coverage.
    ​

  3. Flag missing answers or unclear docs for human review and creation.
    ​

This process ensures that Cora is not just answering reactively, but learning proactively.


πŸ”„ Updating Your Knowledge Base

You can manually update your sources in the Cora App under Settings > Knowledge Sources.

This keeps Cora continuously improving as your product and documentation evolve.

Did this answer your question?