Skip to main content
This major Slack agent release makes it easier to follow what happened after you ask Quivly to do something. Approval and completion messages show the outcome of each requested change, and Quivly handles thread participation more carefully. You also get reply and approval settings for each thread and a clearer view of which accounts need attention.You can ask Quivly to work across customer details, projects, tasks, Notebooks, and supported connected apps without starting a separate conversation for each step.For example:
@Quivly update Acme’s lifecycle stage to Active, create an onboarding project, and draft a Notebook with its open support tickets.
Quivly prepares the changes for review and works through the approved steps. A project creation or a change in a connected app still needs manual approval, even when temporary auto-approval is enabled for eligible updates.

Follow up without starting over

Stay in the same thread to add a detail or change your request. For example, after asking Quivly to set a project due date, follow up with:
Actually, make that Friday.
Quivly uses the thread’s conversation to understand what you mean. You can also ask a follow-up about the answer it just gave, such as:
Which of those support tickets should I follow up on first?
If a requested change has already started, check its result before asking for another change. A follow-up does not undo completed work.

See the result of each requested change

When a request includes several changes, Quivly’s completion message tells you which finished and which still need attention. It distinguishes completed changes from failed, cancelled, skipped, pending, and unconfirmed changes, with links to the updated records when available.For example:
@Quivly update Acme’s onboarding project status to In progress and create a Notebook summarizing its open support tickets.
Review the proposed changes and approve the ones you want. With manual approvals, approving one change does not approve a different change. After the work runs, you can see each result instead of having to work out whether the whole request succeeded.If a change’s outcome cannot be confirmed, Quivly tells you that it may already have taken effect. Check the record before asking it to try again, so you do not accidentally repeat the change.Older progress updates cannot overwrite newer work. Requests that were entirely skipped or cancelled before any change ran also avoid empty completion notices, helping you keep track of the work that matters.

Choose how much detail you want

Quivly now keeps ordinary Slack replies brief by default, so you can find the answer without reading through a long explanation. Important warnings and source links still appear, and you can ask for more detail whenever you need it.Try asking:
@Quivly summarize Acme’s open support tickets.
Then follow up with:
Give me a detailed breakdown of the unresolved issues.
To set a preference for your requests in a thread, open a message’s menu and choose Quivly thread settings. You may find it under More message shortcuts. Set Response length to Brief, Standard, or Detailed, then save. Your choice applies to your requests in that thread, so teammates can keep their own preferences.

Approve routine changes once for a thread

When you are working through several account updates, you can let Quivly make eligible changes without asking you to approve each one. Open Quivly thread settings, set Action approvals to Auto-approve eligible actions, and save.This setting covers project updates, customer updates, and creating Notebooks. For example:
@Quivly update Acme’s onboarding project status to In progress.
@Quivly set Acme’s lifecycle stage to Active.
@Quivly create a Notebook summarizing Acme’s open support tickets.
Auto-approval applies to your pending and new eligible requests in that thread. It does not apply to requests from other people or changes you do not have permission to make. Sharing, publishing, deleting, and actions in external apps still need your approval, as do changes that affect what customers can see.Quivly asks for approval by default. Asking it to “approve everything” in a message does not turn on auto-approval; you must choose it in thread settings.You can select Stop auto-approval at any time. It also expires after 30 minutes without a new request from you, or after eight hours at most. Stopping auto-approval prevents further automatic changes, but does not undo a change already underway.If Quivly thread settings is missing from the message menu, ask your workspace admin to check the Quivly Slack app setup.

See which accounts need attention first

Open Quivly in Slack and select the Home tab. The Accounts to review list now considers both customer health and monthly revenue, helping you focus on accounts where your attention could make the biggest difference.The list shows each account’s health, monthly revenue, what the ranking is based on, and when its health was last scored. You can tell when revenue is unavailable or a health score needs refreshing before you decide what to do.When revenue is missing, current health can still guide the ranking. When health is stale or unavailable, monthly revenue can still help you decide where to look. The Basis column makes these gaps visible.Health scores that are seven days old or older do not raise an account’s priority. If an account has an old score, check its latest activity before acting on it.Use the list to start a conversation:
@Quivly why does Acme need attention? Include its health score and open support tickets.

Keep Quivly involved in the right conversations

Mention @Quivly when you want its help in a channel thread. It can continue relevant follow-ups there and respond in threads it started, including Play and signal posts. Another bot’s reply or a message that simply refers to Quivly does not invite it into a new conversation. Quivly also stays quiet if it cannot read the full thread.For example:
@Quivly summarize the onboarding blockers discussed in this thread.
When you no longer need its help, send:
@Quivly stop
Quivly treats a direct stop request as an instruction to stop participating. A question that happens to contain the word “stop” does not end the conversation, and a stop request addressed to someone else does not silence Quivly.

Search the Slack conversations available to you

Slack conversation searches respect which channels you can currently read and leave out results from channels Quivly can no longer access. For example:
@Quivly find the latest discussion about Acme’s onboarding blockers.
Quivly searches the Slack conversations available to you, so account research stays within your Slack access. Requests to make changes also respect your Quivly permissions and the conversation where you are asking; an internal request does not grant permission to share internal information in a customer channel.