Echo
Builds the deck after a customer call, from what was actually said
Summary excerpt from the creator’s share page. Not independently tested.
What the share page says
Turns a customer call into slides from customer context. What we heard, next steps, project initiatives, or all of the above. Works with Figma or Google Slides, and Granola or Gong notes. On first run, start warm: "Hi, my name is Echo!" Then tell them what you do, using this wording: I turn a customer call (discovery, demo, etc.) into slides based on customer context (what we heard, next steps, project initiatives, or whatever you choose). If you want to update the slides mid-call, stop Granola and type /echo. After setup I can also update those slides when an external call ends, if they want that. Then ask one question at a time: 1. Ask to connect Gmail if it is not connected. Read a few of their sent emails and save how they write (length, formality, words they use or avoid). Use that voice on slide copy. If they decline Gmail, skip the scan and match whatever they tell you about brand and voice. 2. Ask for a template slide (the Figma or Google Slides file and the specific slide to treat as the layout). 3. Ask what they want on the slide using this wording: What we heard, next steps, project initiatives, or all of the above? Anything I should always include or never say? 4. Ask their notes source (Granola or Gong). Then ask for brand guidelines if they have them. If they do not have brand guidelines, use the example deck they already shared as the style source. 5. Ask if they want the slides updated automatically every time an external call ends. If yes, use the post-call routine. If no, stay quiet after calls unless they ask. 6. Remind them: if you want to update the slides mid-call, stop Granola and type /echo. Save those answers. Make sure Gmail (if they agreed), Google Calendar, and the matching deck and notes connectors are installed and connected. Surface install or connect cards in place. After an external call ends, only auto-update if they opted in. Rewrite only the slides they named, using their template and their writing voice. Customer-facing takeaways, not internal sales commentary. Lead with their problem or ask. Three cards is the usual What we heard shape. Write like a person. No em dashes. Never invent what was said. If notes have not synced, wait. Do not add extra slides unless asked. Do not publish or share the deck.
Description as published on the x.ai share page when last checked (2026-11-01).
What its description mentions
Read automatically from the creator's own words and quoted below. Not a test: check the Bot's skills and routines before relying on any of it.
- Apps it names
- GmailGoogle CalendarFigma
- Recurring work
If yes, use the post-call routine
Editorial notes
From the public description, not a test. Written by Grok Bot Wiki from the share-page text; we have not run this Bot. Reviewed .
Best for
Account executives, solutions engineers, and customer success managers who send a recap deck after customer calls and want it drafted from their notes in their own writing style.
Not for
Teams without Figma or Google Slides templates, or whose call notes aren't in Granola or Gong.
What it does
After setup, Echo takes your notes from a customer call and rewrites the slides you named in your own template, covering what we heard, next steps, project initiatives, or all three. It can learn your writing style from a sample of your sent Gmail (optional), follows your brand guidelines or an example deck, and keeps the content customer-facing instead of internal sales commentary. If you opt in, it updates slides automatically after each external call, or mid-call when you pause Granola and type /echo. It never invents what was said, and it waits if notes haven't synced.
First messages to try
- Here's my template slide: [Google Slides link, slide 3]. Put what we heard and next steps on it.
- Use my Granola notes from today's discovery call with [customer] to update those two slides.
- Don't update automatically after calls yet. I'll ask each time.
Apps and accounts
Its description mentions Gmail (optional), Google Calendar, Figma or Google Slides, and Granola or Gong for call notes.
Cautions
- Learning your style from sent email means giving it access to your whole mailbox. Skip that step if your inbox holds confidential deals.
- Automatic updates after every external call edit decks without checking with you each time. It doesn't share decks itself, but review each one before it reaches the customer.
Compare with: Slide Bot by Colin McDermottCall Follow-UpsCustomer Proof Desk
Before you add it
Specific to this Bot, from what its description says:
- It describes recurring work. After adding it, open its routines, confirm the times, and pause any schedule you did not choose.
- It names Gmail, Google Calendar, Figma. Connect those as plugins where one exists rather than signing in through the shared browser, and give it the narrowest access the task needs. What to check for Gmail ↗
The standard checks for any shared Bot
Adding a shared Bot copies its profile, settings, enabled skills, routines, and avatar into your account. It does not copy the creator's computer, logins, conversation history, or memory. Everything it then does runs on your shared Agent Computer with your logins.
- Open the Bot's skills and routines first. Disable any routine before it fires on a schedule you did not choose.
- Check which apps it will try to sign into. Prefer plugins over browser logins, and keep sensitive accounts off the shared computer.
- Set an ask-first rule for anything that sends, posts, pays, or deletes. A listing here is not a test result.
- Give it one small bounded task and read the usage screen afterwards before scaling up.
Related reading: the shared computer permission boundaries the weekly meter
If it misbehaves: Bot not responding routines not running sign-in errors New to Grok Bot? what it is your first task
Attribution
This Bot belongs to its creator, Krista Letz. Facts on this page (name, share link, creator, link status) were read from the public share page. The row was seeded from majiayu000/awesome-grok-bot, ZeroPointRepo/GrokBotDev, cs68614-hash/awesome-grokbot-templates, elie222/botdirectory.ai and kydlikebtc/awesome-grokbot. Imported catalog prose retains CC BY 4.0 attribution; share-page excerpts are labeled separately. Grok Bot Wiki is independent and not affiliated with SpaceXSI (formerly xAI).
Made this Bot? Add a “Listed on Grok Bot Wiki” badge
Optional and free. It links readers to this page and never affects how the Bot is listed. More badge styles ↗
Markdown (README)
[](https://www.grokbotwiki.com/bots/echo)
Or promote this template in the labelled Featured row, from $19.