My requests
Follow the questions you asked colleagues through GuruSup Brain and see where each one stands.
When GuruSup Brain does not have an answer, it can ask a colleague. If you started that request, you can follow it here. It works like a tracking page: you see progress, not the colleague's reply.
My requests is for members. Admins do not get this page. They see the follow-ups for the whole organization in Ingest, see Follow ingestion.
How a request starts
You don't create requests on this page. They start in your assistant.
- You ask your assistant a company question and Brain lacks part of the answer.
- The assistant offers to ask a colleague and names the person Brain would ask.
- You confirm, and the assistant sends the request.
You can also tell the assistant to contact you instead, so you can supply the missing information yourself. The request then appears here too.
The steps, and what the assistant checks first, are in Ask questions. The tool behind it is request_human_info, see the MCP tools reference. The people Brain can ask are the contacts an admin set up in Team, see Brain contacts.
When the colleague answers, Brain adds the answer to its memory, so the next person who asks gets it. The reply itself stays private: this page shows only how the request is going.
Open the page
Click My requests in the sidebar, under Knowledge. The page is titled My knowledge requests. It shows your own requests from the last 90 days, up to 200 of them. Refresh reloads the list.
Before the memory build starts, the page shows a preview with "Available once your memory is built" and "An admin in your organization needs to build it first."
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 Brain 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
Each card shows:
- the subject and a short version of the request,
- the channel it uses, such as Call or Slack, and when it was last updated,
- the reason it ended, when it has ended,
- who started it, for example "Requested by Ana Ruiz · Human Member",
- a list of contact attempts,
- a list of activity events,
- a status badge on the right.
Who started it
The line reads "Requested by [name] · Human Member" for a person, or "Requested by [name] · Agent Account" when an agent account started it.
Contact attempts
Each attempt lists the method used, such as Call or Slack, and for Slack the workspace. It also shows:
- Status: how far the attempt got.
- Outcome: how it ended, when it has.
- Retry: when Brain will try again on its own, when a retry is scheduled.
Request activity
This lists events such as reminders, response versions and expiry, each with a status and time. Some lines add what to do. For example, "We'll retry this automatically, so there's no need to switch contact methods." means Brain will try again without you. "We couldn't reach them this way. Try another contact method." means you should use Try next contact method.
What each status means
| Badge | Meaning | What you do |
|---|---|---|
| Pending, Queued, Delivering | Brain is getting the request ready to send. Queued also shows after a reply, when the answer waits to be learned. | 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 | Brain reminded the person. | Wait. |
| Retry scheduled | Brain will try again on its own. | Nothing. |
| Delivery uncertain | Brain isn't sure the message arrived and will retry. | Nothing. |
| Response received, Waiting, Submitting | The person replied and Brain is taking the reply in. | Nothing. |
| Learning | Brain is adding the answer to its memory. | Nothing. |
| Learned, Revision accepted | The answer is part of Brain's memory. | 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 | Brain 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 | Brain couldn't reach the person with that method. | Use Try next contact method. |
| Not supported | The chosen channel isn't supported yet. | Use Try next contact method. |
| Failed | Something failed on Brain'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. Brain retries. |
| Not ready to answer | The answer is saved and searchable, but linking it to related pages did not finish. | Nothing. Brain retries. |
| Held back | Brain 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 | Brain 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.
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's memory. |
| Organization restart | The organization was restarted. |
| Organization deprovisioned | The organization was deprovisioned. |
Try another way to reach the contact
Try next contact method appears on a request that is Sent, Delivered, Declined, Expired, Delivery failed, Failed or Not supported. Click it. Brain confirms with "Trying the next contact method." and tries the next method the contact has set up that it hasn't used yet, in the contact's order of priority.
Only the person who started the request can use it, and admins for their organization. It is not available when:
| 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. | Brain 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. |
The page shows these after "Could not retry this request".
When the list is empty
You see "No requests in this view" and "Requests you initiate will appear here with their current operational status." Try the All filter first.
If the page does not load
You see "Could not load your requests", followed by a reason. Click Refresh. If it keeps failing, contact support.
Related
- Ask questions: how the assistant asks a colleague.
- Brain contacts: who Brain can ask, and how they are reached.
- How Brain works: how a colleague's answer becomes part of what Brain knows.