Contact Us
If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.
amanda+outlearnkb@helpjuice.com
Article
Last Month
Someone joins your team. On day three they have a question about the refund policy. They search Slack, find a message from eight months ago that might be outdated, and ping the most senior person they can find. That person stops what they are doing, answers, and goes back to work. Multiplied across a team, this happens dozens of times a week. Deploy
Confirmation emails, follow-up messages, summary notifications - these are the communications that should happen automatically but usually require someone to remember to send them. When that person is busy, they get delayed or missed entirely. A customer completes an onboarding flow with your agent. They expect a confirmation email with the details.
Your team needs to know when something important happens in a customer conversation - a high-priority request, a complaint that needs attention, a lead that just came in. Right now that information travels through someone remembering to post it. Which means it often does not travel at all. A customer tells your agent they are considering cancelling
A user completes a flow and should receive a confirmation. A customer submits a request and expects a follow-up. Right now someone on your team manually sends that email. Half the time it goes out late. Sometimes it does not go out at all. Connecting Gmail as an action means your agent sends that email automatically, at exactly the right moment in t
Important conversations should not require someone to manually relay the information to the rest of the team. A new request, a completed form, a flagged issue - these things need to reach the right people immediately, not when someone gets around to posting about them. A customer submits a request through your agent that needs immediate attention fr
A new agent joins your support team. Their first week is mostly spent learning how to phrase things - how formal, how detailed, how to handle a frustrated customer without making it worse. They are good at support but the writing takes three times as long as it will once they find their footing. The quality is inconsistent until it is not. Freshdesk
A lot of how your organisation actually works is documented in email threads - customer-facing explanations, internal process discussions, answers to questions that come up repeatedly. That content is valuable. It is just scattered across inboxes where it is hard to find and impossible to scale. Connecting Gmail as a source lets your agent learn fro
Not every escalation needs a human on the other end right now. Some issues are better handled by a team that reviews it properly, investigates if needed, and responds with a considered answer. Forcing those into a live chat queue creates pressure on your team and sets the wrong expectations for the user. Zendesk Ticketing is the right tool for those
The model your agent runs on shapes how it handles every conversation. Choose the right one and your agent reasons clearly, stays on point, and handles nuanced questions well. Choose the wrong one and you will notice it in the responses. For most teams, the default model handles everyday support questions well - and you will not need to think about
It is 11pm. A customer is on your website trying to figure out why their account is locked. Your chat widget is not there. They send an email and wait. Another customer is in Slack asking your team a question that your agent could have answered in seconds. A third one gives up and opens a support ticket that will sit in a queue until Monday. None of
Your team works through problems in Google Chat every day. The answers are in there - in Spaces, in threads, in the messages where your team documents how things actually work. That knowledge does not have to disappear when the conversation ends. Connecting Google Chat as a source gives your agent access to those conversations. The answers your team
When a conversation needs a human right now - not in a few hours, not via a follow-up ticket, but immediately - your agent needs to be able to transfer it in real time. The user stays in the chat. Your agent hands over. A human takes it from there without missing a beat. Connecting Zendesk Sunshine makes that possible. Live handoffs that land direct
Billing questions are some of the most sensitive and time-critical support conversations your team handles. A customer asking about a charge, a failed payment, or a subscription change needs a fast and accurate answer - not a ticket and a wait. A customer contacts your agent at 8pm on a Friday. They were charged twice this month and want to know why
A handoff that triggers too early makes your agent feel unreliable. A handoff that triggers too late leaves users stuck in a loop with no way out. The difference between the two is almost always in how the trigger was written. Two things go wrong with badly written triggers. The first: a customer asks a general question about billing and gets transf
You have a support problem. Maybe your team is overwhelmed. Maybe customers are waiting too long for answers. Maybe your agent is live but not performing the way you hoped. Whatever brought you here, this page cuts straight to the fix - find your situation below and follow the links. No browsing, no guessing, no reading articles you do not need. My
Your agent has been giving a strange answer to questions about your pricing. You think it might be coming from an old document someone connected last month - but you are not certain. You do not want to delete the source in case you need it. You just need to take it out of play for a few hours while you investigate. Toggling a source off does exactly
It is a Tuesday afternoon. Your agent has been live for two weeks and it has been handling conversations well. Then it stops responding. New messages come in and nothing happens. You check the dashboard and see it: your credit balance hit zero at some point during the day and nobody noticed. Credits are what your agent runs on. Every response uses a
A user lands on your knowledge base. They search, they browse, they open three articles. None of them quite answers their question - the answer exists across two articles but they would have to connect the dots themselves. They give up and submit a support ticket. Your team gets a ticket for something that was technically documented. Embedding your
Not every piece of useful content lives in a platform with an API. Some of it is in a PDF someone emailed around last year. Some of it is on a web page that never made it into the knowledge base. Some of it is in a spreadsheet that three people have a copy of. Manual imports let you get that content into your agent without needing a formal integrati
Content goes out of date. Pricing changes. Products get renamed. Policies get updated. Without something keeping your agent in sync, it keeps answering questions based on information that is no longer accurate - and nobody notices until a customer gets the wrong answer. Auto-sync solves this. When you connect an integration as a knowledge source, Ou
By connecting Google Calendar as an action, your agent can handle scheduling directly in the conversation - checking availability, booking appointments, and confirming details with the user, all in real time. In this article, you'll learn: What your agent can do with Google Calendar as an action How to connect Google Calendar How to configure the a
You have already done most of the work. The documentation exists. The articles are written. The answers are somewhere in your systems. The problem is that your customers cannot find them, and your team ends up answering the same questions manually anyway. It is Monday morning. A customer asks your agent how to export their data. Your agent finds the
By the time you finish this walkthrough, your agent will be connected to your content, configured with clear instructions, and deployed to a real channel. Not a demo. Not a test environment. A working agent that real customers can use today. Most agents that underperform were set up in a hurry. The content step got skipped. The instructions were lef
Your sales and customer data lives in Salesforce. Your customers ask questions that require that data to answer properly. Right now those two things cannot connect during a conversation - someone has to look it up manually and relay it back. A customer asks your agent about the status of their enterprise deal. Your agent does not know - that informa
Two agents can have the same sources, the same model, and the same integrations - and behave completely differently. The instructions are why. It is Friday afternoon. A customer opens the chat frustrated - they have been waiting on a resolution all week. Your agent reads the situation, acknowledges the wait, and responds with exactly the right tone
An action that runs at the wrong moment is worse than no action at all. A scheduling action that fires when someone asks a simple question. A notification that goes out before the user has confirmed anything. Actions that feel random erode trust fast. A user asks your agent a general question about your product. Halfway through the response, a calen
A team deploys to every channel on day one. The widget is on the website, the email channel is connected, the Slack integration is live. A week later, nobody has reviewed a single conversation. The agent is giving mediocre answers on three channels instead of great answers on one. The complexity of managing all of it means nothing gets improved. The
Your agent handles conversations around the clock. Auto-recharge makes sure it never has to stop - when your credit balance runs low, it tops up automatically and your agent keeps going without any interruption or manual action on your part. You set a monthly spending cap so costs stay predictable. After that, you stop thinking about credits entirel
A user has been on your pricing page for four minutes. They have a question - you can tell because they keep scrolling back to the same section. But they do not open the chat. They do not know it is there, or they do not think it can help, or the timing just did not click. They close the tab. An alert message would have caught them. A small nudge at
It is the end of your first month with Outlearn live. You open Analytics and see the numbers: 847 conversations handled, 91% resolved without a human, 4.6 satisfaction rating, and a Content Gaps list showing exactly which questions to add next. You know precisely how your agent is performing, what it is doing well, and what to improve this week. Tha
Effective date: April 22, 2026 These Terms of Service ("Terms") govern your access to and use of the Outlearn platform, websites, applications, AI-powered functionality, integrations, and related services that link to these Terms (collectively, the "Service") and are provided by Helpjuice, Inc. for Outlearn ("Outlearn," "we," "us," or "our"). By acc
You are about to go live with your agent. You are on the Free plan and wondering if Starter is worth it, or if you should jump straight to Growth because you expect decent volume. You spend twenty minutes reading comparison tables and still are not sure. Meanwhile the agent is not live yet. Here is the honest version: start on Starter, go live, and
An agent configured well sounds like your brand, stays on topic, and handles the situations your team deals with every day. An agent configured poorly frustrates users and creates more work than it saves. A well-configured agent is one of the most powerful things your support operation can have. It sounds like your brand, stays focused on the right
A customer has been using your product for two years. They open the chat with a billing question. The first thing your agent asks is their name and email address. They have already typed this into your product dozens of times. They close the chat and email support instead. User Authentication prevents that. When a logged-in user opens the chat, your
Standard integrations let your agent read data from a platform. MCP connections let your agent work inside it - creating records, updating tasks, managing projects, interacting with tools the same way a person would. A customer resolves their issue in chat and asks if a follow-up task can be created in Asana for the implementation team. Without MCP,
Your knowledge base is good. But it was last updated at a specific point in time. The moment something changes - a policy, a price, a product release, an external event your users are asking about - your agent is working with outdated information and has no way to fill the gap. A user asks your agent about a recent change to an integration your prod
Your team documented everything in Confluence - the processes, the product guides, the troubleshooting steps. Most of it never reaches customers because finding the right page requires knowing where to look. Connect Confluence to Outlearn and your agent can surface that knowledge instantly, in the conversation, the moment a customer needs it. A cust
Base URL: https://data.outlearn.com/api/v1 Authentication All API v1 endpoints require a Bearer token in the Authorization header: Authorization: Bearer <api-key> The API key is linked to a specific Agent and Account. All requests are automatically scoped to that agent's account. Response Formats Resource { "data": { ... } } Collection { "data
If your team stores documents, guides, or policies in Box, you can connect it directly to Outlearn. Your agent will be able to draw on that content when answering questions - without you having to copy anything manually. In this article, you'll learn: What happens when you connect Box How to connect your Box account How to manage the connection aft
Useful documentation tends to accumulate in Dropbox over time - product guides, policy documents, reference materials that teams share and update but never formally publish anywhere. That content could be answering customer questions. Right now it is just sitting in a folder. Connecting Dropbox gives your agent direct access to those files. No manua
Build a completely custom deployment using your agent's API - for teams that need more than the standard channels offer. Your product has a built-in help panel. You want your Outlearn agent to power it - same knowledge, same instructions, same quality - but surfaced inside your own UI instead of a standard widget. There is no pre-built option for th
Your Helpdocs articles were written to reduce support volume. Connecting them to Outlearn is the fastest way to make that happen - your agent reads the articles, understands them, and delivers the right answer to the right customer the moment they ask. Your Helpdocs library has sixty articles. Your support team still gets the same twenty questions e
A customer asks your agent to check the status of their installation request. Your team manages those in an internal system your engineering team built three years ago. There is no Outlearn integration for it. There never will be - it is custom, it is yours, and nobody else uses it. Without a way to reach it, your agent has to tell the customer to c
It is month two. The person who set up the agent is on holiday. Three new questions have appeared in Content Gaps that nobody has acted on. A source went out of sync last week and nobody resynced it. A customer got a wrong answer yesterday because an article was updated in the knowledge base but the agent was not told. None of this happens when more
Auto-sync keeps your sources up to date automatically - but sometimes you want to trigger an update right now, without waiting for the next automatic sync cycle. A manual resync pulls in the latest content from your source immediately. In this article, you'll learn: When to use a manual resync How to resync a source What to expect during and after a
Your Help Scout documentation already contains the answers your customers need. The problem is that most customers never find them on their own. Connect Help Scout to Outlearn and your agent delivers those answers directly in the conversation - no searching, no browsing, no waiting. You published a Help Scout article answering the most common questi
If a source is no longer relevant, outdated beyond repair, or was connected by mistake, you can delete it from your agent. Deletion is permanent and cannot be undone, so make sure you're certain before proceeding. In this article, you'll learn: What happens when you delete a source How to delete a source How to delete an individual snippet When to d
Your customers should not be able to ask your agent about internal pricing, HR policies, or employee onboarding. Your employees should not get customer-facing answers when they need internal process documentation. The same agent can serve both audiences - but only if you tell it which content belongs to which. Every source and snippet in Outlearn ha
Your team's Google Drive is full of useful content that never makes it into your knowledge base - product guides, policy documents, onboarding materials, process docs. Customers ask questions those files could answer. Your agent just cannot reach them yet. Connecting Google Drive gives your agent access to that content directly. No copying, no refor
One agent trying to serve everyone usually ends up serving no one particularly well. Your internal HR team starts using the same agent as your customers. Within a week, a customer asks a question and gets a response that references an internal onboarding process. An employee asks about benefits and gets a customer-facing answer about your refund pol
It is possible to go from no account to a live AI agent answering real customer questions in a single afternoon. This is the first step. Creating your Outlearn account takes less than two minutes. Once you are in, you will be taken straight into a guided setup flow that walks you through connecting your content and deploying your agent step by step.
The teams that set up Outlearn fastest are not the ones with the most technical experience. They are the ones who spent five minutes understanding how the pieces fit together before touching a single setting. Outlearn is built around five concepts: your Agent, Sources, Actions, Handoffs, and Deployment. Each one has a clear job. Once you understand
Every conversation your team has resolved in Intercom represents a problem that has been understood and answered. That institutional knowledge does not have to disappear into a closed conversation. It can become part of what your agent knows. Your most experienced support person has resolved hundreds of conversations in Intercom. They know how to ha
A customer emails you. They say your agent told them the wrong cancellation policy and they were charged for another month. You know the policy is in your knowledge base. You need to know exactly what the agent said, why it said it, and whether it is saying the same thing to other people. Conversation and Training is where you go. Every exchange you
Your KnowledgeOwl content exists because someone took the time to document the answers. Connecting it to Outlearn means those answers get used - not just by customers who happen to search in the right place, but by every customer who asks a relevant question, automatically. Your team spent months building a KnowledgeOwl library. The articles are tho
Your finance team needs the invoice for last quarter. Or you noticed an unexpected charge on your card and want to understand what it was. Or you are putting together expense documentation and need a PDF with the billing details on it. All of that is on the Billing page. Every charge, every period, every invoice - downloadable as a PDF in one click.
You built your Helpjuice knowledge base to help customers find answers on their own. Connecting it to Outlearn takes that one step further - instead of customers searching for articles, your agent finds the right answer for them and delivers it instantly in the conversation. A customer opens your knowledge base, searches for "how do I reset my passw
By connecting Calendly as an action, your agent can handle scheduling directly in the conversation - checking availability, booking appointments, and confirming details with the user, all in real time. In this article, you'll learn: What your agent can do with Calendly as an action How to connect Calendly How to configure the action trigger and re
A customer asks when their order will arrive. A prospect wants to book a demo. A user needs their account reset. These are not questions that need an answer from a knowledge base. They need something to actually happen. Actions are what make that possible. They turn your agent from a tool that answers questions into one that resolves problems end to
Some of the best answers in your organisation are not in any knowledge base. They are in Slack threads. The engineer who explained that bug fix in #engineering. The CS lead who wrote out the correct refund process in #support. The onboarding doc someone shared in #general six months ago. Connecting Slack as a source lets your agent learn from those
Your team communicates in Microsoft Teams every day and a lot of that communication contains useful knowledge: answers to common questions, troubleshooting tips, process explanations, and more. By connecting Microsoft Teams as a source, your agent can tap into that institutional knowledge and use it to answer questions. In this article, you'll lear
Every resolved ticket in Zendesk is a documented solution to a real customer problem. That history is one of the most valuable knowledge assets your team has - and most of it is sitting unused in a closed ticket queue. A customer contacts your agent with an issue your team resolved for someone else eight times last quarter. The solution is sitting i
A customer opens the chat on your website. The widget is a different shade of blue than everything else on the page, and the name in the header is "AI Assistant." They close it. Not because the agent is bad - they never found out. The widget did not feel like part of your product. Five minutes of branding changes that entirely. Your colors, your log
Not every team has a helpdesk platform. Not every escalation needs one. Sometimes the right answer is a summary email to the right person, and someone follows up. Simple, direct, no overhead. Your support team is four people. You do not use Intercom or Zendesk. When a customer conversation needs human attention, you just need someone on your team to
Most support teams spend the majority of their time on questions they have already answered before. The same how-do-I questions, the same troubleshooting steps, the same links sent a hundred times. An AI agent changes that equation. It handles the questions that do not need a human so that the humans on your team can focus on the ones that do. In Ou
Your team maintains documentation in OneDrive - Word documents, PDFs, guides that get updated regularly and shared across the organisation. That content is already the source of truth for your team. Connecting it to Outlearn makes it the source of truth for your agent too. Your agent reads the files in OneDrive and uses them to answer questions, s
Some conversations need a human the moment they escalate. The user is frustrated, the issue is sensitive, or the question requires judgment that no AI should be making alone. When that moment comes, your agent should be able to hand off instantly - with the full conversation already in your team's hands, not a blank inbox and a user who has to start
Your team has a Spaces channel for general questions. Some questions get answered quickly. Others get one reply that leads somewhere and then trail off. A few never get a response at all. The quality of the answer depends entirely on who happens to be watching the channel that day. Deploy your agent to Google Chat and every question in that channel
The moment your agent cannot help someone is the moment that person's experience either holds together or falls apart. If there is nowhere for that conversation to go, the user hits a wall. They repeat themselves to the next person they reach. They leave frustrated. They do not come back. A customer has been trying to resolve a billing dispute for t
Fourteen users asked your agent about your new pricing tier this week. Your agent had no idea what to say to any of them. It told them it did not have that information and suggested they contact support. Fourteen tickets, for a question that should have been handled automatically, because nobody added the content after the pricing change went live.
Order status. Shipping updates. Product availability. These are the questions e-commerce customers ask most - and they all require live data from your Shopify store to answer accurately. Without that connection, your agent can only offer generic responses while customers wait for a human to look it up. A customer asks where their order is. Your agen
You want your agent to help customers check their order status. You add your order management system as a source. The agent learns about orders in general - but when a customer asks about their specific order, it still cannot tell them. It can describe what an order status is. It cannot look one up. That is the difference between a source and an act
It is Monday morning. Your support inbox has 47 unread emails from the weekend. A third of them are asking the same three questions. Another third are straightforward issues your agent could resolve in seconds. The rest need a real person. Your team spends the first two hours of the week clearing the backlog before they can get to anything else. The
Everything is ready. The sources are connected, the instructions are written, the branding looks right. You have tested it in the preview panel and the answers are good. The only thing left is putting it on your website - and that is a single copy-paste away. This article gets you through that last step. No developer required, no build process, no d
Your team answered the same question fourteen times today. Tomorrow it will be fifteen. Meanwhile, your documentation is sitting in a tab nobody opens, doing nothing. Outlearn fixes both of those problems at once. It is an AI support agent that connects to everything you already have: your knowledge base, your documents, your website, your tools. It
Most teams using Custom API Actions are connecting to systems they already run their business on. This article lists the most common ones, grouped by category, with a one-line description of what each connection enables and a link to the API documentation you will need to set it up. Before you start, read Creating a Custom API Action for the setup p
The verified MCP library covers the most common platforms. But your stack might include tools that are not on the list - internal systems, niche platforms, or services your engineering team has built MCP support for themselves. Your engineering team built MCP support into your internal ticketing system six months ago. It is not on the verified list
Every support team has a list of questions they answer the same way every single time. The password reset. The refund window. The shipping cutoff. These do not live in a knowledge base article. They live in someone's head, or a pinned Slack message, or a doc nobody can find. Snippets are the fastest way to get those answers into your agent. You writ
You open Analytics on a Monday morning. Your Auto-Solved rate dropped 12 points last week. You do not know why yet - but you know exactly where to look. The Handoff Reasons panel shows the same topic triggering escalations over and over. The Content Gaps panel has three new entries that were not there the week before. In ten minutes you have a clear
Your agent gets a message: "Hi, I was charged twice this month." They know the answer. They open the billing docs, find the right section, copy the relevant part, rewrite it in a tone that fits the conversation, add a closing line, and send. Four minutes for something they have done thirty times this week. With Outlearn as a Copilot in Intercom, the
A user opens the chat widget. The welcome message says "Hi! How can I help you today?" They type something vague back. The conversation meanders. Compare that to a widget that opens with "Ask me anything about your account, billing, or getting started" - the user immediately knows what to ask, asks it well, and gets a useful answer. The welcome mess
Your Freshworks ticket history is a record of every problem your customers have ever had and every solution your team has ever provided. Most teams never use that data for anything after the ticket is closed. Connecting it to Outlearn changes that. Your support team has been using Freshworks for two years. In that time they have resolved thousands o
This is a auto-generated Article of all your definitions within the glossary. Glossary This is a auto-generated Article of all your definitions within the glossary. All A C D E H K M S T W Action A task your agent can perform during a conversation, such as sending an email, booking a meeting, or updating a record. Agent An AI-powered assistant con
Someone posts a question in a Teams channel at 4pm on a Friday. The people who know the answer are in meetings or have already signed off. The post sits there over the weekend. On Monday, someone eventually replies - but by then the person asking has already made a decision without the information they needed. Deploy your agent to Microsoft Teams an
Effective date: April 22, 2026 Outlearn, Inc. ("Outlearn," "we," "us," or "our") provides the Outlearn website, platform, applications, and related services (collectively, the "Service"). This Privacy Policy explains how we collect, use, disclose, and otherwise process Personal Data when you access or use the Service, interact with us, or communicat
Your team closes 80 tickets a day. Twenty of them require real investigation. The other sixty are variations of questions they have answered before - password resets, billing explanations, feature how-tos. Each one still takes three to five minutes to write up properly. That is three to five hours a day spent composing answers that already exist som