Product Updates//Updated /3 min read

Calls That File Themselves at the Bottom of Your Chat

Calls in your project chat used to leave their card where the call began, so the summary ended up buried above everything said since. Now the card moves to the bottom when the call ends, and again when the transcript and summary are ready. Here is how to start a call and use what it leaves behind.

By Jason Gordon

Founder & CEO, Specloop

Specloop release 1.301: calls that file themselves at the bottom of your chat

You can call our team straight from your project chat. After the call you get a transcript and a short summary: what was discussed, what was decided and who's doing what next. From release 1.301, that summary lands at the bottom of the conversation, where you look first.

Start a call from the chat

  1. Open Support chat in the sidebar and choose the conversation for your project.
  2. Check the language picker next to the Call button. Pick the language you'll be speaking so the transcript comes out right.
  3. Press Call. The call opens with video and screen share, and the chat stays open beside it.
A project conversation in the client portal with the language picker and the Call button at the top right
The Call button and language picker sit at the top of every conversation. Names shown are examples.

While the call is live, its card in the chat shows the call in progress, and anyone on the project can join it from there.

Where the card goes when the call ends

The call's card is posted when the call starts. Before this release it stayed there. By the time the summary arrived, the conversation had often moved on, so the summary sat several messages up where nobody looked. Now the card moves itself:

  1. When the call ends, the card moves to the bottom of the chat.
  2. When the transcript and summary are ready, usually a few minutes later, it moves to the bottom again, in case people kept chatting in the meantime.

It's the same message moving, not a copy. Read receipts and reactions stay with it, and anyone who already has the chat open sees it slide into place without refreshing.

A call card at the bottom of a chat showing the call length, a summary, decisions, a Show transcript link and Add to project and Share buttons
After the call, the card sits at the bottom with the summary, the decisions and the action items. The content shown is an example.

Use what's on the card

The card shows how long the call lasted, then three parts:

  • Summary: a few sentences on what the call was about and where it landed.
  • Decisions: one line for each decision actually made.
  • Action items: one line for each follow-up, starting with who owns it.

Underneath:

  • Show transcript opens the full transcript, labelled by speaker.
  • Add to project files the summary in the project's notes.
  • Share passes it on.
  • The copy button on the card copies the summary, ready to paste into an email or a document.

Links mentioned on the call are clickable in both the summary and the transcript, and open in a new tab.

Why it matters

A call is often where the real decisions get made. If the record of it is hard to find, decisions get forgotten or argued over later. With the summary at the bottom of the conversation, the whole team can see what was agreed without hunting for it. There's more on how chat works inside each project in our post on project chat.

Tips

  • Start the call from the right conversation. The summary lands in the thread the call started in, so start it in the project it's about.
  • Say decisions out loud. "So we're agreed, the booking page goes live Friday" turns into a clean line under Decisions.
  • Name who's doing what. Action items are written with an owner when the call makes it clear.

Frequently asked

Questions people ask about this

  • No. Transcripts and summaries are made automatically after a call with our team, and the card moves into place on its own.

About the author

Jason Gordon

Jason Gordon

Founder & CEO, Specloop

Jason Gordon is the founder of Specloop, a spec-driven AI development studio that builds production-grade business applications from a complete specification, in weeks, at flat rate, with 100% code ownership. He also builds GeoTest, a free tool that scores how visible a site is to AI search engines. He writes about AI search, spec-driven development, and why most AI builds never reach production.

Follow Jason on LinkedIn →

Keep reading

Next step

Want a spec for your build?

We write the full specification before any code is generated, then ship in 30–60 days at one flat rate. You own every line.