What it connects to

OmniScale is the CRM underneath

OmniScale holds the contracts, the texts and the emails, and the agreement you sign to join lives there too. When our team books a job, an OmniScale webhook posts it to your portal, and that feed is what your Sales tab shows.

Leads come through the same door. Your OmniScale new-lead workflow sends each one to your shop's lead address with its source on it, and that source is what attribution reads.

What Google sends

Connect your Google account with one click and we read spend and nothing else. Google Ads and Google Local Services are read on their own and kept on separate lines, in the weekly card and in attribution, where each is set against the customers it brought. When we run your ads the spend comes through our manager account, so there is nothing to connect. Either way the Google figures fill in by themselves each week.

What Urable sends and gets back

Paste your Urable key in Connections and your jobs feed into Scale Command: jobs, revenue, average ticket, our share of your revenue, busiest days and service mix. Attribution reads the jobs and the payments on them, which is how it knows when a lead turned into a paying customer.

Leads travel the other way. A new lead from your OmniScale workflow is added to your Urable as a customer, and one already in there is skipped.

The money runs through Square

Square is behind Pay now and the card on file: the invoice, the button that settles it, and auto-pay when you turn it on. The plan is paid in the page at join, and Home shows your balance with a Pay now button too.