Understand GurusupUse cases

Use cases

Six real questions that need more than one source to answer, who asks them, which sources answer them, and what to set up in Gurusup.

Use these to decide what to connect first. Each case lists what an admin sets up, so you can copy the setup that fits your team.

No single tool answers these questions. Slack has the conversation, Notion has the write-up, HubSpot has the deal, and a PDF has what was signed. Gurusup keeps what it learned from all of them in Brain, one company memory, and returns the evidence, with references, to your assistant. What comes back depends on what your sources contain. If the evidence is not there, the assistant is told to say so.

QuestionWho asksSources that answer it
What is the state of this renewal?Account managerHubSpot, Slack, Notion
What discount did we agree, and is it signed?Sales lead, financeHubSpot, Slack, uploaded contracts
Has this incident happened before?On-call engineerWebhook, Slack, Notion
How do expense approvals work?New hireNotion, uploaded PDFs, Slack
What is our current price?Sales, supportNotion, uploaded price list, Slack
Give me the weekly account health summaryCustomer successHubSpot, webhook, Slack

Prepare for a renewal call

"I have a call with Acme tomorrow. What's the current state of their renewal?"

Who asks: an account manager, the day before the call.

SourceWhat it adds
HubSpotThe deal's stage, linked contacts and recent activity
SlackWhat the team said about Acme, including a discount argument that never reached the CRM
NotionThe account plan

Set up: connect HubSpot (use Import history to bring in deals from before you connected), Slack with the app invited to the customer channels, and Notion with the account plans shared. Slack brings in no earlier history, so invite the app early. The account manager needs the categories the material sits in, for example sales and customers.

Check what was actually agreed

"What discount did we offer Globex, and is it in the signed contract?"

Who asks: a sales lead before a renewal, or finance before invoicing.

SourceWhat it adds
HubSpotThe deal and its notes
SlackThe discussion where the discount was negotiated
Uploaded filesThe signed contract, which lives nowhere but a PDF

Set up: connect HubSpot and Slack, then upload the signed contracts. PDFs, Word files and ZIP archives are accepted (Content types and limits). Check the usage estimate in the upload dialog before you confirm. Scanned PDFs without a text layer are skipped as Unsupported. If the contract and the chat disagree, Gurusup can raise a conflict for an admin.

Find out whether we have seen this incident before

"Checkout is timing out again. Has this happened before, and what fixed it?"

Who asks: the engineer on call, in the middle of an incident.

SourceWhat it adds
WebhookAlerts or incident events your monitoring tool sent
SlackThe thread where the team debugged it last time
NotionThe runbook

Set up: create a webhook source and point your monitoring or incident tool at its URL. Gurusup learns only what the tool sends, so send the fields a person needs later, such as a title and a description. Invite the Slack app to the incident channel and share the runbooks in Notion.

Onboard someone new

"How do we handle expense approvals, and who do I ask if it's over budget?"

Who asks: a new hire in their first week.

SourceWhat it adds
NotionThe policy in the handbook
Uploaded filesThe PDF version HR keeps
SlackA recent answer from finance about an exception

Set up: share the handbook in Notion, upload the PDFs that live outside it, and invite the Slack app to the finance help channel. Invite the new hire as a member and grant the categories they should read: a new member starts with none. Optionally, set up the person who owns expenses as a Gurusup contact, so the assistant can offer to ask them when Brain has nothing on it. The new hire follows that request under My requests.

Settle two versions of the same fact

"What is our current price for the Pro plan?"

Who asks: anyone in sales or support, mid-conversation with a customer.

SourceWhat it adds
NotionThe pricing page, updated last quarter
Uploaded filesAn older price list PDF
SlackA message saying the price changed

When one source clearly replaces another, with a later date or an explicit correction, Gurusup treats the newer one as current. When two sources really disagree and Gurusup cannot tell which is right, it raises a conflict.

Set up: connect the sources, and have an admin or a member keep an eye on Conflicts. They confirm one alternative, says each is true in a different context, writes the correct statement, or dismisses the case. An admin can also Ask a contact first. See How conflicts work.

Turn a recurring analysis into a skill

"Give me the weekly health summary for my accounts, the way we did it last time."

Who asks: a customer success manager, every Monday.

SourceWhat it adds
HubSpotDeals and activity
WebhookProduct usage figures your own system sends
SlackThe week's customer conversations

Set up: connect HubSpot and Slack, and create a webhook source for the usage data. Write the steps of the analysis as a skill and give it a clear description: the assistant decides whether to load a skill by reading it. A skill sent by an assistant arrives as Pending, and the assistant cannot use it until an admin approves it on Skills.

Choose what to connect first

If your questions are aboutStart with
Customers and dealsHubSpot, Slack customer channels, uploaded contracts
How the company worksNotion, uploaded policies, the main team channels in Slack
Incidents and operationsA webhook from your tools, the incident channel in Slack, runbooks in Notion

Start with two or three sources that answer one real question, and add more once you see what comes back. Check Ingest to confirm content was learned, and keep an eye on usage.