Getting started with QuoteCloud

Post quote news to each team's Teams channel

In a larger business one channel for every quote gets noisy fast. A Zap sends each quote's news to the channel of the team or region that owns it.

Start free 14-day trial Book a demo

Build a Zap with QuoteCloud's Zapier app, on Essentials and up. Document Status Changed (set to Sent), Recipient First Viewed Document or Document Signing Complete starts it; Paths by Zapier picks the team from a value such as the document's owner; Microsoft Teams' Send Channel Message posts to that team's channel.

Last reviewed by the QuoteCloud team

Two illustrative team chat channels with sample data. Behind, Tallowmere Insurance Brokers' Commercial › Quotes channel: posts from a Zap when fleet insurance TI-F-0334 for Bramblewood Couriers was sent ($24,420.00), when Lena Moretti first viewed Lantern Lane Café's recommendation TI-Q-2241, with Sophie Varga replying that she's calling, and when Lena and Josh signed it ($4,108.00). In front, the Personal lines channel with Jack Mendoza's home and contents quote TI-P-1180 sent and first viewed.

Why give each team its own channel?

Tallowmere Insurance Brokers quotes business, fleet, apartment and personal cover from four teams. A single channel for every quote would mean the personal lines brokers scroll past fleet renewals all day, and the director can't see at a glance how the commercial team is going.

So each team has a Quotes channel in Microsoft Teams, and the Zaps send each quote's news to the channel of the team that owns it: sent, first viewed, signed. The team sees its own pipeline; nobody else's gets in the way.

  • Route on a value the QuoteCloud event carries, such as the document's owner. Check your test data for the field.
  • Regions work the same way: one path, or one Zap, per region's channel.
  • Who can read each channel is set in Teams: the IT admin side.

How do I post each quote to its team's channel?

One Zap per moment: this one is for quotes going out. Every name is the exact event you pick in Zapier.

ZapQuote sent: post to the owner's team

  1. When QuoteCloudTriggerDocument Status ChangedWith the Document Status input set to Sent.Passes on
    • Document title
    • Reference
    • Client
    • Total
    • Owner
  2. Paths Paths by ZapierPathsOne path per team, on the document's owner.
    • CommercialOwner is Sophie Varga or Arun Pillai
    • Personal linesOwner is Jack Mendoza
    • ApartmentsOwner is Leilani Fox
  3. Then Microsoft TeamsActionSend Channel MessageIn each path, with that team's channel.Mapped in
    • Team
    • Channel
    • Message Text

No Paths on your Zapier plan? Build one Zap per channel with a Filter by Zapier step on the owner instead. The same job can be built in Make, bring your own, with Make's Microsoft Teams modules.

Arun Pillai sends Bramblewood Couriers' fleet quote on Friday afternoon. It lands in Commercial › Quotes with the client, the $24,420.00 total and Arun's name; the personal lines channel stays quiet.

Result

Each team's channel reads like its own pipeline, and the director can watch any of them without the noise of the others.

QuoteCloud's Zapier app: Essentials and up

How insurance brokers connect QuoteCloud

Viewed and signed in QuoteCloud, posted to Commercial

Tallowmere Insurance BrokersInsurance recommendation TI-Q-2241 Sample · fictional business

Activity

  1. Sent to Lena and Josh MorettiTue 20 Oct, 10:15 am · by Sophie Varga
  2. First viewed by LenaTue 20 Oct, 11:40 am · posted to Commercial
  3. Signed by Lena and JoshThu 22 Oct, 7:10 pm · 2 of 2 · posted to Commercial
  4. Broker fee paid$363.00 by card through Stripe

Accept the recommendation and pay the broker fee

2 of 2 signed

  • Lena MorettiCo-owner SignedThu 22 Oct, 6:52 pm
  • Josh MorettiCo-owner SignedThu 22 Oct, 7:10 pm

What you're accepting

Premium, as quoted
$3,745.00
Broker fee incl. tax
$363.00
Total
$4,108.00

Certificate of authenticity and audit trail attached

TI-Q-2241: first viewed by Lena, then signed by Lena and Josh, broker fee paid.

Zaps

  1. Recipient First Viewed Document
  2. Document Signing Complete
  3. Send Channel Message

Commercial › QuotesTallowmere Insurance Brokers · channel · 14 members

Illustration · sample data

  1. Sales automationsFri 16 Oct · 2:20 pmPosted by a Zap

    Sent: TI-F-0334 · Fleet insurance for Bramblewood Couriers

    Client
    Bramblewood Couriers
    Total
    $24,420.00
    Owner
    Arun Pillai
    Valid until
    Fri 30 Oct

  2. Sales automationsTue 20 Oct · 11:40 amPosted by a Zap

    First viewed: TI-Q-2241 · Lantern Lane Café

    Viewed by
    Lena Moretti
    Owner
    Sophie Varga

    Sophie Varga 11:43 am
    Calling Lena while she has it open.

  3. Sales automationsThu 22 Oct · 7:10 pmPosted by a Zap

    Signed: TI-Q-2241 · Lantern Lane Café

    Signed by
    Lena & Josh Moretti
    Total
    $4,108.00
    Owner
    Sophie Varga
    Broker fee
    Paid

    Helen Carrow Fri 23 Oct · 8:05 am
    Good result. Cover is in place well before the 14th.

Illustration with sample data, not Microsoft Teams’ screen.

Commercial › Quotes: each moment posted by a Zap, with the team's replies under it.

The channel is our illustration of a team chat with sample data, not Microsoft Teams' screen.

Field map for the team posts

Sent, first viewed and signed Zaps: QuoteCloud fields and where they land in the Teams message
Microsoft Teams: Microsoft Teams fieldDirectionQuoteCloud: QuoteCloud fieldGoes intoExample (sample data)Note
Every team post
Team and Channel (per path) QuoteCloud to Microsoft Teams Owner (the Paths rule) Message field Commercial › Quotes Check the owner field's name in your test data.
Message Text: the heading QuoteCloud to Microsoft Teams Reference and document title Message field Sent: TI-F-0334 · Fleet insurance for Bramblewood Couriers
Message Text: client QuoteCloud to Microsoft Teams Client Message field Bramblewood Couriers
Message Text: total QuoteCloud to Microsoft Teams Total Message field $24,420.00
First viewed and signed
Message Text: viewed by QuoteCloud to Microsoft Teams Recipient name Message field Lena Moretti
Importance (optional) QuoteCloud to Microsoft Teams A fixed value, after a Filter on the total Message field high Only for quotes over an amount you choose.

All values are sample data.

Variations on this recipe

  • First views and signatures

    Copy the Zap and swap the trigger for Recipient First Viewed Document or Document Signing Complete. Same paths, same channels.

  • Regions instead of teams

    Give each region a channel and one path, or one Zap with a Filter, per region, on the owner or a value your template carries.

  • Flag the big ones

    Add a Filter by Zapier step on the total, and set Send Channel Message's Importance to high only for quotes over your limit.

  • Post as the Zapier bot

    Microsoft Teams' Send Bot Message posts to a public channel from the Zapier bot. It needs the Zapier app installed from the Teams Store: the IT admin side.

  • Expired and lost too

    Document Expired and Document Lost can post to the same channels, so the team sees what slipped. Or chat the owner instead.

  • Build it in Make instead

    Bring your own: Make's built-in OAuth connection to QuoteCloud and QuoteCloud's API or Zapier endpoints, beside Make's own Microsoft Teams modules. There's no ready-made QuoteCloud app on Make, so you design each step.

Give every team its own feed

QuoteCloud's Zapier app is on the Essentials plan and up. Start a free 14-day trial and route your first quotes to a test channel.

Start free 14-day trial Book a demo

Build the team posts in five steps

  1. Make the channels

    Create a Quotes channel in each team in Microsoft Teams, and add the account your Zaps will post as.

  2. Start with Document Status Changed

    In Zapier, choose QuoteCloud's Document Status Changed, set the Document Status to Sent, and load a recently sent test quote.

  3. Add the paths

    Add Paths by Zapier with one path per team, each with a rule on the document's owner (or the field your test data shows).

  4. Post in each path

    In each path add Microsoft Teams' Send Channel Message, pick that team and channel, and map the reference, title, client and total.

  5. Test, then copy

    Send a quote to an @example.com address, check the right channel, switch the Zap on, then copy it for first views and signatures.

Questions about team posts

Can QuoteCloud post to a different Teams channel for each team?

Yes, through Zapier. One Zap with Paths by Zapier sends each quote to its team's channel, based on a value in the QuoteCloud event such as the document's owner. Without Paths on your Zapier plan, build one Zap per channel with a Filter.

Which QuoteCloud events can post to a channel?

Any of QuoteCloud's Zapier triggers. For quote news the usual ones are Document Status Changed set to Sent, Recipient First Viewed Document and Document Signing Complete. Document Expired, Document Lost and Document Paid can post too.

Will every quote post, or only the ones we choose?

Only the moments you build a Zap for, and only the quotes that pass its filters. Leave an event out and the channel stays quiet for it; add a Filter on the total and only the larger quotes post.

Who can read the posts?

Whoever is a member of the channel in Microsoft Teams. QuoteCloud sends only the fields you map, and Teams' own membership decides who sees them, so pick channels that suit the details you post.

More Microsoft Teams questions

More on QuoteCloud and Microsoft Teams

Five use cases with the exact Zapier steps, then how to connect, the IT admin side, the limits and the cost.

Every team, its own quote feed.

Start a free 14-day trial and route QuoteCloud's sent, viewed and signed news to each team's channel in Microsoft Teams.

Start free 14-day trial Book a demo

See pricingQuoteCloud on ZapierAll integrations