Skip to content
RAYON OPSTHE SERVICING DESK · FOR COMMERCIAL BROKERAGES

Every servicing call that reaches a producer costs a sale. Rayon Ops finds the leads, answers intake, fills the submissions, turns each request into a ticket, and checks every certificate before it leaves.

The product

One platform. Eight modules.

From the first call to the signed binder, on one client record. Start with one module or run all eight. Click through the product below.

Rayon OpsAM

Lead engineEvery quiet quote worked, every week

Gets the agency found in search and AI answers, and works every quote that went quiet.

Quiet quotes3
Northline Fiber
Quoted in June
Corbel Fire Protection
Quoted in May
Aster Glazing
Quoted in April
Contacted2
Halden Electric
Follow-up 3 of 5
Pike Mechanical
Follow-up 1 of 5
Replied1
Ridgeway Mechanical
Wants a per-project aggregate
Booked1
Halden Electric
Producer call Fri 10:00

How it runs today. Leads depend on referral partners, and old quotes are never called again.

Product screens shown with sample data. Names and times are made up.

The desk never binds, changes coverage or gives coverage advice. Those need a licence and stay with your staff.

What it gives back

Count the hours you get back.

Put in your own volumes. The platform takes the keying, the chasing and the first answer; your people keep the judgement and the client.

Your work todayPer monthMinutes eachHours
Certificates issuedCertificates module38
Other servicing requestsTickets module67
New and renewal submissionsSubmissions module45
Inbound calls taken by producersIntake module30

The starting figures are placeholders. Replace them with your own: every result on the right is your numbers multiplied out, not a Rayon result.

125
hours a month back to your team
out of 179 hours spent on this work today
0.8
full-time people, at 160 hours a month
$52,675
of staff time a year, at your hourly cost
  • 74%

    of agents name re-keying as their top workflow pain.

    Ivans, 2026 Carrier-Agency Connection Report

  • 86%

    of agents still prefer customer service to run through the agency by phone.

    Big “I”, 2026 Agency Universe Study

  • About 60%

    of agency errors and omissions claims come from commercial lines.

    IA Magazine on Swiss Re Corporate Solutions data, 2020

Verify your COI

Nothing leaves without four checks.

Plenty of tools produce a certificate in seconds. None tells you how often it is wrong. Change any line on this one and watch the checks decide.

VERIFY YOUR COI · CHANGE ANY LINEsample, not real data
What the certificate says
What the policy file holds
  • PASSIs it ours?The producer block matches your agency.
  • PASSDoes it read back?Dates and policy number in the finished PDF match the record.
  • BLOCKDoes it contradict itself?The additional insured box is ticked, and the description says “certificate holder only”.
  • BLOCKIs every claim sourced?Not yet: the waiver of subrogation has no CG 24 04 on file.
Held. 2 checks failed

Who presses send

The desk earns each kind of send, one at a time.

  1. 1Watch. The desk drafts and checks. Your staff send everything and see what would have been blocked.
  2. 2Named sends. You clear specific routine cases, such as a renewal certificate to an existing holder with unchanged wording.
  3. 3Wider. The cleared list grows only where the record shows nothing blocked.
  4. 4Always a person. New holders, new wording, anything touching money, anything a licence is needed for.

What we count

An error is a sent document that states something the policy does not support, or has to be sent again. Published monthly from the first month of live work.

  1. ·Blocked before send. Drafts stopped by one of the four checks.
  2. ·Escaped defects. Sent documents later found to misstate coverage.
  3. ·Reissues. Certificates sent again with a changed field.
  4. ·Same-day rate. Requests closed on the day they arrived.

Ticketing and the client record

Every request is a ticket. Every client has one record.

Most servicing goes wrong between people, not inside a document: a request nobody owns, a promise nobody wrote down. The desk keeps both in one place. Pick a ticket to see its history and the client behind it.

QUEUE · EVERY OPEN REQUESTillustration
TICKET 1042 · CERTIFICATEPriya · due Today 2:00
  1. 9:12Call answered. Certificate for a new general contractor.
  2. 9:14Holder’s name and address requested by text.
  3. 9:15Client told to expect it by 2:00.
Client record · Ridgeway Mechanical
Policies
General liability · auto · workers compensation · umbrella
Holders on file
14, each with the wording it was last sent
Open work
Certificate 1042 · endorsement 1044
Last conversation
Call at 9:12 today, summary attached

One ticket per request

Whether it arrives by phone, email or text, it gets a requester, an account, a type, an owner and a due date.

A status anyone can read

Waiting on the client, waiting on the carrier, ready for your approval, or done. Nothing lives in one person’s inbox.

One record per client

Policies, holders and their wording, every conversation and all open work, in front of whoever picks up next.

It sits beside your management system

Policies and billing stay where they are. The ticket links to them and the finished document is filed back.

Send us a real request.

  • Any servicing requestA certificate, an endorsement, loss runs, a renewal, a billing question. Send a real one and we run it on the call.
  • A free audit of 50 certificatesOnes you have already sent. You keep the findings either way.
  • We read every request ourselvesNo sequence of automated emails follows this form.

Questions brokers ask.

Software, with a desk behind it. Your team logs in to the same screens shown on this page, and our people can run any module for you.

Certificates, endorsement and policy change requests, loss runs, renewal and new business submissions, cancellations and lost policy releases, billing questions, premium audits and first notices of a claim. Each becomes a ticket with an owner and a due date.

A ticket is one servicing request written down once: who asked, for which account, what they need, who owns it, when it is due and what is still missing. It replaces the email that sits in one person’s inbox, so anyone can see what is open and nothing depends on memory.

No. Your management system stays the record for policies, billing and documents. The client record holds what it usually does not: every request, every conversation, each holder’s wording and the work still open.

Generating a certificate is the easy part. The costly part is a certificate that states something the policy does not grant. The four checks look for that, whatever produced the document.

It does not go out. The ticket goes to your staff with the reason, for example that the waiver box is ticked and no waiver endorsement is on file, and the client is told what is needed and when to expect it.

Bind, change coverage or give coverage advice, or send a new kind of document without a person’s approval. Those need a licence and stay with your staff.

Named people on the desk, working under a login you issue and can switch off. It is used only to do your work.

Per finished piece of work, with the price on this page before the first paid desk starts. No seats and no hourly rate.

Send one real request with the form on this page. We run it on a 30-minute call, then audit 50 certificates you have already sent. The desk begins in watch mode, where your staff still send everything.

The library11 longer answers on certificates, loss runs, renewals and tickets