Getting started with QuoteCloud

Keep Slack channels quiet: only the moments that matter

Every QuoteCloud event can post to Slack. Most shouldn't. Pick the moments, send each to the people who act on it, filter by value and digest the rest.

Start free 14-day trial Book a demo

Build one Zap per moment that matters, not one per QuoteCloud event. Post Document Signing Complete to a wins channel, send first views and comments to the owner with Send Direct Message, add Filter by Zapier's Only continue if... for value or template, and collect expired quotes with Digest by Zapier. Leave drafts and status changes in QuoteCloud.

Last reviewed by the QuoteCloud team

Two overlapping panels with sample data, both illustrations of a generic team chat. Behind, before: Plinthwork's #sales channel with a Zap posting every QuoteCloud event, documents created, status changes, deliveries, an open, a resolved comment, and the sales director asking whether anyone saw the client open the renewal. In front, after: #deals with a single post for a signed deal over the team's threshold.

Why do QuoteCloud alerts get noisy?

QuoteCloud's Zapier app has more than twenty triggers. Connect each one to the same channel and #sales fills with drafts created, statuses changed and emails delivered, and the one message that mattered, Mossbank opening their renewal, scrolls past before the sales director sees it.

People mute a channel like that within a week. The fix isn't fewer Zaps; it's choosing who each moment is for, and posting nothing else.

  • A channel post is for news the whole team acts on or celebrates.
  • A direct message is for news one person acts on.
  • A digest is for news nobody needs until the weekly meeting.
  • Everything else stays in QuoteCloud, where it's always one click away.

Where should each QuoteCloud event go?

Plinthwork's #sales before, and the plan the team moved to.

The jobBefore: all into #salesAfter: to the people who act
Signed deals Recipient Signed Document posted every signature, so a two-signer deal posted twice. Document Signing Complete, over the team's threshold, to #deals: win celebrations.
First opens Every open posted to #sales; nobody knew whose call it was. Recipient First Viewed Document as a direct message to the owner: opens & comments.
Comments Created, resolved and reopened comments all posted. New comments only, filtered, as a direct message to the owner.
Approvals Approvers found out when the rep asked. Document Review Requested as a direct message to the approver: approval nudges.
Payments Amounts posted to a channel half the company could read. Payments to a private #finance channel: payments to finance.
Expired and lost A post each time, ignored. One Friday digest: expired digest.
Drafts, statuses, deliveries Document Created, Document Status Changed and Document Delivery Status Changed, all day. Not posted. They're in QuoteCloud's dashboard; a bounced email can still go to the owner.

How does one Zap send big wins to #deals and the rest to the owner?

Paths by Zapier sends each signed deal one of two ways.

ZapSigning complete: route by value

  1. When QuoteCloudTriggerDocument Signing CompleteFires once every signer has signed.Passes on
    • Document number
    • Total
    • Owner email
  2. Paths Paths by ZapierPathsSplit on the document's total.
    • Path A · $1,000 a month or moreSend Channel Message to #deals, for the whole team.
    • Path B · everything elseFind User by Email, then Send Direct Message to the owner.

No Paths on your Zapier plan? Build two Zaps with opposite Filter by Zapier conditions instead.

Calloway Retail Group signs PW-2355 on Tuesday afternoon and it goes to #deals. A small add-on signed the same hour goes to Theo as a direct message, where he's glad to see it and nobody else needs to.

Result

The channel keeps its meaning: when something posts there, it's worth reading.

QuoteCloud's Zapier app: Essentials and up

How software teams run renewals in QuoteCloud

Only new comments, never the housekeeping

ZapComment event: new comments only

  1. When QuoteCloudTriggerDocument Comment EventFires when a comment is created, resolved or reopened.Passes on
    • Event type
    • Comment text
    • Owner email
  2. Only if Filter by ZapierFilterOnly continue if... the event type is created.
  3. Then SlackSearchFind User by EmailSearches on
    • Email
  4. Then SlackActionSend Direct MessageMapped in
    • User (from the search)
    • Message Text

Dana Whitcombe's question on PW-R-2291 reaches Theo; Theo resolving it an hour later doesn't send anything.

Result

One message per question, to the person who answers it.

QuoteCloud's Zapier app: Essentials and up

The owner's news, in the owner's messages

After the change, Theo's direct messages carry his own documents: approved, opened, a question. Nothing in #deals is about one person's pipeline, and nothing for Theo is lost in a channel.

  • Send Direct Message to the owner found by Find User by Email.
  • One message per moment: approved, first opened, new comment.
Build the owner messages
Team chat · direct messagePlinthwork Illustration · sample data

Quote alertsDirect message · to Theo Marchetti

  1. Quote alertsPosted by a ZapMon 10:42 am

    Approved: Hollis Grant approved PW-R-2291. It's ready to send.

    Send PW-R-2291 from QuoteCloud

  2. Quote alertsPosted by a ZapTue 9:16 am

    Opened: Dana Whitcombe has opened PW-R-2291 for the first time.

  3. Quote alertsPosted by a ZapTue 11:05 am

    New comment on PW-R-2291 from Dana Whitcombe:

    “Can we start at 140 and add the new depot's team in July?”

    Reply in QuoteCloud

Illustration with sample data: a generic team chat, not Slack's screen. The Zap writes every word you see in its posts.

A channel people keep unmuted

QuoteCloud's Zapier app is on the Essentials plan and up. Start a free 14-day trial and plan your channels with a test quote.

Start free 14-day trial Book a demo

More ways to keep it quiet

  • Filter on the template

    If only order forms matter, Only continue if... the template is the order form. Renewals and add-ons can have their own rules.

  • Digest what can wait

    Digest by Zapier collects entries and posts them once, daily or weekly. Expired and lost quotes are the classic case.

  • One channel, one audience

    #deals for the team, a private #finance for amounts, direct messages for owners. Don't mix audiences in one channel.

  • Schedule for working hours

    Slack's Send Channel Message and Send Direct Message can schedule a message for later, so a signature at 11 pm can wait for the morning.

  • Leave housekeeping out

    Document Created, Document Status Changed and delivery updates are rarely worth a post. QuoteCloud's dashboard has them.

  • In Make, the same rules

    Bring your own: Make's filters and routers do the same job between QuoteCloud's API or Zapier endpoints and Make's own Slack modules.

Cut the noise in five steps

  1. List your Zaps

    In Zapier, list every Zap that starts with a QuoteCloud trigger and posts to Slack.

  2. Name the audience

    For each, decide: the whole team, one owner, finance, or the weekly meeting.

  3. Move owner news to direct messages

    Swap Send Channel Message for Find User by Email and Send Direct Message.

  4. Add filters and digests

    Only continue if... for value, template or comment type; Digest by Zapier for what can wait.

  5. Turn off the rest

    Switch off Zaps on drafts, statuses and deliveries, and tell the team which channel means what.

Questions about noisy channels

How do I stop QuoteCloud alerts flooding a Slack channel?

Post only the moments the whole team acts on, such as Document Signing Complete, to a channel. Send first views and comments to the owner as direct messages, add Filter by Zapier's Only continue if... for value or template, and collect expired quotes into one digest.

Which QuoteCloud events are best left out of Slack?

Usually Document Created, Document Status Changed and Document Delivery Status Changed. They're useful in QuoteCloud's dashboard but rarely need a post. A delivery failure is the exception: Document Delivery Failed can message the owner so they can fix the email address.

Can one Zap post big deals to a channel and small ones to the owner?

Yes, with Paths by Zapier, if your Zapier plan includes it: one path posts to the channel above an amount, the other sends the owner a direct message. Without Paths, build two Zaps with opposite Filter by Zapier conditions.

Can a late-night signature wait until morning?

Slack's Send Channel Message and Send Direct Message on Zapier can schedule a message for later. Working out the next morning's time needs an extra step, such as a formatter, so test it before you rely on it.

More Slack questions

More on QuoteCloud and Slack

Six use cases with the exact Zapier steps, then how to connect, what goes into each message and what it costs.

Fewer posts. Every one worth reading.

Start a free 14-day trial of QuoteCloud and plan your Slack channels around the moments that matter.

Start free 14-day trial Book a demo

See pricingQuoteCloud on ZapierAll integrations