Skip to content
Integrations Guru

Guru + Finn.

Guru integration with Finn. Guru helps teams maintain and find shared company knowledge and answers.

What you can do with Guru.

Guru helps teams maintain and find shared company knowledge and answers.

Resolve a service request with the right company procedure

Finn uses Guru's company guidance to carry a routine request through the actual service action and a recorded employee response.

Typically handled byEmployee service desk specialist

Starts when

An employee submits a routine service request through connected chat or the service desk.

What Finn handles

  1. Find the relevant accessible Guru cards, check their recorded verification context, and collect the request details needed to follow the company's procedure.
  2. Obtain the service owner's decision where required, then complete the permitted booking, account update, or fulfillment action through the connected system that owns the service.
  3. Confirm the result, send the employee a clear response with useful source links, and close the connected service record with the action evidence and Guru guidance used.

The result

The employee's request is completed and the service record connects the result to the company procedure.

Turn a repeated customer question into maintained knowledge

Finn converts a verified support resolution into a reviewed Guru card and returns that knowledge to the support workflow.

Typically handled bySupport knowledge editor

Starts when

A recurring customer question receives a confirmed resolution in the connected support tool.

What Finn handles

  1. Read the resolution and related Guru cards, identify the missing guidance, and remove private customer details before writing the reusable explanation.
  2. Create or revise the card with symptoms, concrete instructions, and source references, then collect the knowledge owner's publishing and verification decisions.
  3. Publish the accepted card to its intended collection, link it in the connected support record, and send the support team the final guidance through connected messaging.

The result

The recurring issue has accepted reusable guidance and a support record showing where the knowledge came from.

Finish a sales answer package from trusted company knowledge

Finn completes buyer questions using Guru's company knowledge and records the delivered response and next step in the CRM.

Typically handled bySales enablement specialist and proposal coordinator

Starts when

A buyer sends a set of questions to the connected sales inbox.

What Finn handles

  1. Read the buyer's CRM context, match each question to current Guru cards, and identify claims requiring a product or commercial owner's decision.
  2. Complete the response in the connected document tool, cite its source cards, and collect missing decisions rather than improvising policy or pricing.
  3. Send the accepted response through connected email, attach it to the CRM opportunity, and record remaining questions and the buyer's next agreed action.

The result

The buyer receives a completed answer package and sales retains the exact response and source context.

Run a knowledge verification cycle to completion

Finn coordinates the review work behind Guru's trust indicators so outdated cards receive a real owner decision and accepted corrections.

Typically handled byKnowledge operations coordinator

Starts when

A defined set of Guru cards reaches its verification review date.

What Finn handles

  1. Read the cards, their verification state, and assigned verifiers, then compare the instructions with current evidence from the connected business and document tools.
  2. Send each verifier the specific confirmation or correction needed, collect their decisions, and apply accepted edits without treating a routine text change as a verification decision.
  3. Record the verifier's accepted status through Guru's verification workflow, notify the intended team of material changes, and close the connected review tasks with final card links.

The result

The reviewed card set has actual verifier decisions and accepted corrections, with the review work recorded as complete.

Carry an operating policy change into everyday work

Finn connects an accepted policy update in Guru to the routine task, communication, and record changes needed to put it into practice.

Typically handled byBusiness operations change coordinator

Starts when

A policy owner accepts a change to an operating procedure.

What Finn handles

  1. Read the accepted policy and affected Guru cards, identify the business workflows it changes, and collect any remaining implementation decisions from the responsible owners.
  2. Revise and publish the accepted cards to the existing audience, then update the corresponding instructions or records in the connected service and project tools.
  3. Send the affected team the practical change notice through connected messaging, complete the agreed coordination tasks, and record the final guidance and work results.

The result

The accepted policy is reflected in accessible guidance and the connected operating workflow, with the change communicated to its users.

Complete a role-specific onboarding journey

Finn builds a new teammate's practical onboarding around the right Guru knowledge and carries the accompanying coordination work through completion.

Typically handled byPeople operations onboarding coordinator

Starts when

A confirmed new hire enters the connected HR onboarding process.

What Finn handles

  1. Read the new hire's role and the team's accessible Guru onboarding cards, then deliver a private guide focused on the tools, procedures, and contacts the role actually needs.
  2. Book introductions through the connected calendar and create equipment or application requests in the connected service systems, following their responsible owners' access decisions.
  3. Answer routine follow-up questions with source-linked guidance, track fulfillment and completed learning tasks, and update the connected HR or project checklist.

The result

The teammate receives relevant guidance and introductions, with setup and onboarding tasks recorded through their actual completion.

Set up the connection around your work.

Contact Finn to discuss the records your workflow needs and the actions you want it to perform.

Your team chooses what Finn can access, what agents can change, and when a person must approve the work. The connection needs the appropriate account access and permissions from Guru.

Put your Guru integration to work.

Tell us which records, actions, and teams the connection needs to support.