Chat

What Chat Does

Springbase Chat helps you work with AI using your own knowledge, documents, and live data.

Instead of asking a model generic questions, you can connect a Context. A Context is Springbase's knowledge base and memory layer. When a Context is attached or mentioned, Springbase can retrieve relevant source material and use it to ground the assistant's response.

Use Chat when you want to ask questions, create drafts, analyze documents, summarize knowledge, compare information, or turn source material into useful output.

Quick Start

1. Create or open a Context.
2. Add documents, meeting notes, or live sources.
3. Open Chat from that Context, or mention it with @context-name.
4. Ask a specific question.
5. Tell Springbase the format you want: bullets, table, memo, email, checklist, or short answer.
6. Save useful assistant outputs back into a Context when you want to reuse them later.

That is the core loop:

Add knowledge -> ask grounded questions -> create useful output -> save what matters.

What You Can Do In Chat

With Springbase Chat, you can:

• Ask questions using one or more Contexts
• Use @mentions to reference a specific Context in your prompt
• Start a chat directly from a Context
• Generate summaries, drafts, checklists, briefs, emails, and analysis
• Use shared Contexts that collaborators maintain with you
• Save useful assistant outputs back into a Context for future retrieval
• Work with live data when a Context has connected live sources

Key Concept: Contexts

A Context is a focused knowledge base. It is how Springbase gives the assistant memory about your work.

A Context can include:

• Uploaded documents
• Searchable document chunks
• Live sources
• Live pages and crawl logs
• Metadata such as name, description, category, tags, visibility, and source visibility

When you use a Context in Chat, Springbase retrieves relevant information from that Context and uses it to make the answer more specific, factual, and useful.

When To Use Chat

Start A Chat From A Context

If you already know which Context you want to use, start there.

1. Open the Context you want to use.
2. Choose Use in Chat.
3. Springbase creates a new chat and attaches the selected Context.
4. Ask your question.

Example

If you have a Context called Investor Relations, you could ask:

Draft this month's investor update using the latest material in this Context.

Or:

Summarize all open questions investors asked last quarter.

Springbase will use the attached Context to ground the response.

Use @mentions In Chat

You can reference a Context directly in your prompt using @mention.

As you type @, Springbase suggests Contexts you can access. Choose the right Context, then write the task you want done.

Example Prompts

Summarize the latest objections from @acme-enterprise.

Draft a follow-up email using the pricing notes and technical requirements in @acme-enterprise.

Create a board-prep checklist from @investor-relations.

Generate next week's content ideas from @client-brand.

Find the escalation path in @support-runbook.

Write Better Chat Prompts

For best results, give Springbase three things:

Simple Prompt

Summarize @support-runbook.

Better Prompt

Using @support-runbook, summarize the current escalation process for billing issues.
Return the answer as a short checklist for a support agent.

Strong Prompt

Using @support-runbook, create a customer-ready response for someone reporting a billing issue.
Include:
- A short apology
- The first troubleshooting step
- The escalation path
- A friendly closing

Use Chat With Shared Contexts

Springbase supports shared Contexts. A Context owner can invite specific people by email to help maintain the Context while keeping it private or controlled.

Shared Contexts are useful when multiple people contribute knowledge, such as:

• Founder knowledge bases
• Sales account workspaces
• Investor relations folders
• Client project workspaces
• Research repositories
• Support runbooks

What Editors Can Do

If you are invited as an editor, you can:

• Read the shared Context
• Upload documents
• Delete documents
• Reprocess failed documents
• Add or remove live sources
• Save assistant outputs into the Context
• Save meeting content into the Context
• Use the shared Context in Chat retrieval

What Editors Cannot Do

Editors cannot:

• Invite more people
• Revoke collaborators
• Change sharing settings
• Delete the Context

Example

A sales lead creates a Context for a strategic account and invites the account executive, sales engineer, and customer success manager. In Chat, the team can ask:

Summarize the latest objections from @acme-enterprise.

Draft a follow-up email using the pricing notes and technical requirements.

What did they care about most in the last meeting?

This keeps account knowledge in one place and lets the AI answer from the combined record.

Save Useful Chat Outputs To A Context

If the assistant creates something useful, save that output back into a Context.

Saved assistant output can include message details such as:

• Message ID
• Chat ID
• Role
• Content
• Model name

Save Output Behavior

If you are an invited editor on a shared Context, you can save useful model output into that shared Context when you have edit content access.

Use Chat With Live Data

Contexts can include Live Sources, which keep selected knowledge updated from web pages or connected apps.

Live data support can include:

• Auto-updating sources from web and connected apps
• Service ingestion for tools such as Slack, GitHub, and Notion
• Scheduled syncs
• Crawl and sync logs
• Per-item tracking
• Source health management

Example Prompt

Using @product-updates, summarize the latest changes from our connected sources.

Use Live Sources when the information changes often and you do not want the assistant working from last week's knowledge.

Understand Chat Output

Springbase Chat can render rich, structured responses. Depending on the answer, output can include:

• Markdown
• Code blocks
• Tables
• Math
• Inline images
• Citations
• Canvas artifacts for richer outputs such as code, HTML, React, SVG, Mermaid, and Markdown

For source-grounded work, review citations and source references so you can verify where the answer came from.

Example Workflows

Investor Update Workflow

Use this when preparing investor communications.

Using @investor-relations, draft this month's investor update.
Include:
- Key product progress
- Customer or sales highlights
- Risks or open questions
- Next month's priorities

You can also ask:

Summarize all open questions investors asked last quarter.

Investor relations Contexts often include pitch decks, financial model notes, monthly updates, board meeting notes, and investor Q&A.

Sales Account Workflow

Use this for account research, follow-ups, and objection handling.

Using @acme-enterprise, summarize the latest objections from the account.
Return:
- Objection
- Source or context
- Suggested response
- Follow-up owner

You can also ask:

Draft a follow-up email using the pricing notes and technical requirements.

A sales account Context can include call notes, CRM exports, proposals, objection handling, competitive intel, and mutual action plans.

Client Project Workflow

Use this when working with client material.

Using @client-brand, generate next week's content ideas.
Match the client's tone and include 10 options.

You can also ask:

Summarize unresolved feedback from @client-brand.

A client project Context can include discovery notes, brand docs, meeting transcripts, strategy docs, content calendars, and design feedback.

Research Workflow

Use this when working across documents, PDFs, notes, and data exports.

Using @policy-research, compare the findings across these papers.
Return a table with:
- Paper or source
- Main claim
- Evidence
- Limitations

You can also ask:

Extract all claims about regulatory risk.

Research repository Contexts can include PDFs, web captures, notes, data exports, and summaries.

Support Runbook Workflow

Use this for grounded support responses.

Using @support-runbook, answer this customer question:
[Paste customer question here]

Return:
- Customer-ready answer
- Internal note
- Escalation path if needed

Support runbook Contexts can include troubleshooting docs, known issues, product FAQs, escalation rules, and internal notes.

Tips For Better Results

Be Specific About The Context

Instead of:

What should I do next?

Try:

Using @acme-enterprise, recommend the next three follow-up actions based on the latest call notes and objections.

Ask For A Format

Instead of:

Summarize this.

Try:

Summarize @investor-relations as:
- 5 bullet points
- 3 risks
- 3 recommended follow-ups

Ask For Evidence-Based Answers

If you want the assistant to stay close to the source material, say so:

Using only @support-runbook, answer this customer question.
If the Context does not contain enough information, say what is missing.

Break Big Tasks Into Smaller Tasks

Instead of one giant request:

Analyze everything in @client-brand and create a strategy.

Try:

First, summarize the client's positioning from @client-brand.

Then:

Now turn that into 5 campaign angles.

Then:

Create a launch announcement using the strongest angle.

Permissions And Access

What you can do in Chat depends on your access to the Context.

Direct collaborators can edit Context content, but they cannot manage access unless they own the Context.

Public, Private, And Unlisted Contexts

Springbase supports these Context visibility options:

Public Contexts can also include publishing metadata such as tagline, cover image, category, tags, source visibility, published date, equip count, weekly active users, query activity, and ratings.

Troubleshooting

I Cannot Find A Context With @mention

Possible reasons:

• You may not have access to the Context.
• The Context may not exist.
• You may not be signed in with the account that has access.
• If it is a shared Context, your invite may not be accepted or linked yet.

Shared Context invites require the invitee to sign in before they can access or edit the Context.

I Can Read A Context But Cannot Edit It

You may only have read access. Editing content requires edit content access.

Public or unlisted viewers should not see owner/editor controls such as upload document, delete document, add live source, reprocess document, share settings, or delete Context.

I Cannot Invite Someone To A Shared Context

Only users with manage access can invite or revoke collaborators. In most workflows, that means the Context owner manages email sharing.

Direct collaborators cannot invite more people or change access settings.

I Saved Output But It Did Not Appear As Expected

The save-output flow includes duplicate detection. If the output was already saved, Springbase may identify it as a duplicate instead of creating another copy.

Review the save response summary for saved, duplicate, and failed counts.

Best-Practice Prompt Templates

Summarize A Context

Using @context-name, summarize the most important information.
Return:
- Executive summary
- Key details
- Open questions
- Recommended next steps

Draft An Email

Using @context-name, draft an email to [audience].
The goal is to [goal].
Use a [tone] tone.
Include:
- Short subject line
- Clear opening
- 3 key points
- Specific call to action

Create A Checklist

Using @context-name, create a checklist for [task].
Group the checklist into:
- Preparation
- Execution
- Follow-up

Extract Risks

Using @context-name, extract all risks mentioned in the available material.
Return a table with:
- Risk
- Evidence
- Severity
- Suggested mitigation

Compare Documents Or Notes

Using @context-name, compare the main points across the available documents.
Return:
- Areas of agreement
- Areas of disagreement
- Missing information
- Recommended decision

FAQ

What Is A Context?

A Context is a Springbase knowledge base used during Chat. It can include uploaded documents, searchable chunks, live sources, and metadata.

Can I Use A Shared Context In Chat?

Yes. If you have access to a shared Context, you can use it in Chat retrieval.

Can I Save Assistant Responses Into A Context?

Yes. Springbase supports saving assistant chat output as documents in Contexts. Invited editors can also save useful model output into shared Contexts when they have edit content access.

Can Contexts Update Automatically?

Yes. Use Live Sources for auto-updating data from web pages and connected apps.

Can Collaborators Delete A Shared Context?

No. Direct collaborators can help maintain Context content, but they cannot delete the Context unless they own it.