My requests
Follow the questions you asked colleagues through Gurusup and see where each one stands.
When Gurusup does not have an answer, it can ask a colleague. If you are a member and started that request, follow it here, and try another way to reach the colleague when they don't answer. It works like a tracking page: you see progress, not the colleague's reply.
Admins don't get this page. If an admin opens its address, they land on Ingest, which shows the follow-ups for the whole organization. See Follow ingestion.
How a request starts
You don't create requests here. You ask your assistant a company question, Gurusup lacks part of the answer, the assistant offers to ask a colleague, and you confirm. You can also ask it to contact you so you supply the answer yourself. See Ask a colleague and the request_human_info tool in the MCP tools reference.
When the colleague answers, Gurusup adds the answer to Brain, so the next person who asks gets it. The reply itself stays private.
Open the page
Click My requests in the sidebar, in the Brain group. The page is titled My knowledge requests, with "Follow the Human Information requests you initiated. Contact responses remain private; this view shows only safe operational progress." It shows your own requests from the last 90 days, up to 200 of them. Refresh reloads the list. While it loads you see placeholder cards.
Read the counters
Five counters sit at the top of the page:
| Counter | What it counts |
|---|---|
| Total | All your requests |
| Live | Requests in progress, for example queued, sent or delivered and waiting for a reply |
| Response / closed | Requests past the sending stage: answered, declined, expired, cancelled, or waiting to be learned |
| Processed | Requests whose answer Gurusup has learned |
| Needs attention | Requests that failed, were held back, or could not be read |
Learning has a filter but no counter, so the counters may not add up to Total. The counters cover the requests on this page, from the last 90 days and up to 200. A few statuses are counted under one counter and appear under another filter, so a filter can show slightly different numbers than its counter.
The filter buttons under the counters narrow the list: All, Live, Response / closed, Learning, Processed and Needs attention.
Read a request card
| Part of the card | What it shows |
|---|---|
| Subject and request | A short version of the request. Without a subject: "Knowledge request". Without text: "No request detail available." |
| Channel and time | Call, Email, Slack or WhatsApp, and when it last changed, for example "5m ago". |
| Requested by | "Requested by [name] · Human Member", or "· Agent Account" when an agent account started it. |
| Contact attempts | Each method tried (for Slack, the workspace), with Status, Outcome once it ended, and Retry when Gurusup will try again on its own. |
| Request activity | Events such as Reminder, Response version and Expiry, each with a status and time. |
| Reason | Why it ended, once it has. See Why a request ended. |
| Badge | The status, on the right. See What each status means. |
Some activity lines tell you what to do:
| Line | What it means |
|---|---|
| We'll retry this automatically, so there's no need to switch contact methods. | Gurusup will try again without you. |
| We couldn't reach them this way. Try another contact method. | Use Try next contact method. |
| We couldn't confirm the call went through. Automatic follow-up has stopped. | Gurusup could not tell whether the call reached the person and does not switch channels. There is no Try next contact method, because another request could contact them twice. Contact support if you need help. |
| The answer is saved. Adding it to your memory failed on our side and we've been alerted. | Nothing to do on your side. |
| The answer is saved. It will be added once your usage credit renews or increases. | Your organization ran out of usage. Ask an admin, see Plan and usage. |
What each status means
| Badge | Meaning | What you do |
|---|---|---|
| Pending, Queued, Delivering | Gurusup is getting the request ready to send. Queued also shows after a reply, when the answer waits to be learned. A call can also wait in Pending until a set time, see below the table. | Nothing. |
| Sent | The request went out and no reply yet. | Wait. You can use Try next contact method. |
| Delivered | The message reached the person. | Wait. You can use Try next contact method. |
| Reminder sent | Gurusup reminded the person. | Wait. |
| Retry scheduled | Gurusup will try again on its own. | Nothing. |
| Delivery uncertain | Gurusup isn't sure the message arrived and will check again. For a call it checks up to three times, then stops and the request shows Failed. | Nothing. |
| Response received, Waiting, Submitting | The person replied and Gurusup is taking the reply in. | Nothing. |
| Learning | Gurusup is adding the answer to your company memory. | Nothing. |
| Learned, Revision accepted | The answer is part of Brain. | Nothing. Ask your question again. |
| Declined | The person declined. | Use Try next contact method, or ask someone else. |
| Expired | Nobody answered in time. | Use Try next contact method, or ask again. |
| Retired | Gurusup closed the request. | Ask again if you still need it. |
| Paused | The answer is saved. Learning resumes when your usage renews or is raised enough. | Ask an admin about usage, see Plan and usage. |
| Waiting to withdraw | Knowledge from this request is being withdrawn. | Nothing. |
| Withdrawn | The knowledge was withdrawn. | Nothing. |
| Delivery failed | Gurusup couldn't reach the person with that method. For a call, this includes a number saved without a country code: Gurusup does not call it. | Use Try next contact method. If the number is the problem, ask an organization admin to add the country code in Team, see Contacts. |
| Not supported | The chosen channel isn't supported yet. | Use Try next contact method. |
| Failed | Something failed on Gurusup's side. | Nothing to do on your side. Contact support if it matters. |
| Not searchable yet | The answer is saved, but isn't searchable yet. | Nothing. Gurusup retries. |
| Not ready to answer | The answer is saved and searchable, but linking it to related pages did not finish. | Nothing. Gurusup retries. |
| Held back | Gurusup held the update back because it didn't pass its quality checks. | Nothing to do on your side. Contact support if it matters. |
| No access | Gurusup could not read the item. | Contact your admin. |
Requests that were cancelled, referred to someone else or opted out of show that word as their badge, in the Live filter.
A call can also stay Pending on purpose: the person is already on a call with Gurusup, it is outside their contact hours, or Gurusup spaces out contact with them. The app shows no reason. Your assistant does, with the time in UTC, for example "It's outside [name]'s contact hours, so we'll call at [date and time] UTC." See Tools.
If no method is left and the number has no country code, your assistant says "We couldn't call [name] because their phone number needs a country code. Ask an organization admin to add it in Contacts, then ask again."
Why a request ended
When a request has ended, the card says why:
| Reason | Meaning |
|---|---|
| Accepted, Completed | The request finished as planned. |
| Declined by contact | The person declined. |
| Expired unanswered | Nobody answered. |
| Cancelled | The request was cancelled. |
| Slack contact link removed | The person's Slack link was removed. |
| Slack contact link replaced | The person's Slack link was replaced. |
| Slack workspace disconnected | The Slack workspace was disconnected. |
| Knowledge withdrawn | The answer was withdrawn from Brain. |
| Organization restart | The organization was restarted. |
| Organization deprovisioned | The organization was deprovisioned. |
| We couldn't confirm the call went through. Automatic follow-up has stopped. | Gurusup checked a call that may or may not have connected, could not confirm it and stopped. See Read a request card. |
Try another way to reach the contact
Find the request
The button shows on requests that are Sent, Delivered, Declined, Expired, Delivery failed, Failed or Not supported. It does not show on a call Gurusup could not confirm.
Click Try next contact method
Gurusup confirms with "Trying the next contact method." It uses the next method the contact set up and hasn't been tried, in the contact's order, and only on the channels the assistant allowed.
Only the person who started the request, and admins of the organization, can do this. When it can't be done, you see "Could not retry this request" and one of these:
| Message | Why |
|---|---|
| Brain is already following up on this question with other people on its own, so it can't be sent again by hand. The answer will show up here. | Gurusup is coordinating several people for this question. |
| This question already has an answer, so it won't be sent to another contact method. | A reply already came in. |
| This question was already sent through every contact method this person has. | There is no method left to try. |
| The person this question was sent to is no longer a contact. Ask someone else instead. | An admin removed the contact. |
| This question is still on its current contact method. You can try another one once it has been sent or has failed. | The request is not in a status listed above. |
| This question was closed before it could be sent. | The request ended while you clicked. |
| This question no longer exists. Refresh the page. | It was removed. Click Refresh. |
| Only the person who asked this question or a workspace admin can send it again. | You did not start this request. |
| We couldn't confirm this question was sent. Refresh the page to see where it stands. | Gurusup is not sure the new attempt went out. Click Refresh before trying again. |
| We couldn't send this question. This is on our side. Try again in a few minutes, and contact support if it keeps failing. | Nothing was sent. Try again later. |
If the page looks wrong
| You see | What to do |
|---|---|
| "No requests in this view" and "Requests you initiate will appear here with their current operational status." | Try the All filter. |
| "Could not load your requests", followed by a reason | Click Refresh. If it keeps failing, contact support. |
| "The questions Gurusup asks your team for you" under "Available once your memory is built" | The memory is not built yet. See Overview. |