How the apps connect.

The bsns.ccapps don’t just share a login — they share a tenant, a customer record, an inbox, and a task surface. Most SMB tools sell you isolated systems and leave the integration as your problem. We’ve made the integration the product.

Here are the cross-app paths that matter most. Some happen automatically, and some depend on the apps and providers your tenant has enabled.

One person, one record

When you hire someone in crew, their record is the same record that:

• rideuses to track the driver’s license expiry and medical card date.
• autouses for the technician’s shop floor productivity.
• rent uses for the property manager assignment.
• work uses to fan out onboarding tasks the day they start.

You don’t maintain separate driver / tech / manager rosters. One employee, one update, propagates everywhere.

One customer, one record

The ties Customer is the same record that:

• auto shows as the vehicle owner on a repair order.
• rent attaches to a commercial occupant.
• bill sends invoices to.
• loop threads conversations against, even if the customer texts in cold.

Update a phone number once and every app sees the change.

Every customer-facing message goes through loop

ride confirms a trip, auto pings a customer that their car is ready, rent reminds an occupant about rent, bill sends an invoice, rsvpconfirms a booking — all of them route through loop. So:

• One inbox for incoming customer replies, regardless of which app sent the original message.
• One provider configuration (Twilio or Telnyx). Set it up once.
• Consent and opt-out are tracked centrally, not re-implemented per app.

Every reminder lands in work

Cross-app reminders — an overdue invoice in bill, a stuck loopthread, a driver’s license about to expire, a lease coming up for renewal — spawn tasks against the right person and surface them on work. You don’t open every app to find what needs attention; you open work.

The work /inboxis the activity feed for that stream: every assignment, comment, due-date change, and overdue reminder shows up newest-first. You can complete, snooze, or reply right from the inbox row. A “since you last looked” divider tracks where you left off, so a busy day doesn’t mean re-reading everything you already triaged.

Your day lives in work

The work /today planner fuses your real calendar with suite work: Google Calendar events, rsvp bookings, native events, tasks, and bill due dates. Untimed work stays in the agenda rail; timed work and meetings sit on the grid.

Public booking links still live at rsvp, but scheduling setup now lives in work under /schedule. That keeps resource availability, Google/Zoom connections, bookings, and the planner in the same operational surface.

Workflows decide what happens next

The vertical apps create the business objects. rsvp creates a booking. A public form creates a response. bill sends an invoice. pact sends or completes a document. Those apps should stay focused on owning their records.

Workflows live in workand decide what happens after one of those objects exists. A form response can create an owner task. A booking can resolve a contact. A stalled signature can notify the right person. That is how the suite can adapt to a tenant's process without hard-coding every vertical app to every other app.

Documents flow through pact

Anything that needs a signature or an attestation routes through pact:

• crew offer letters.
• rent leases and renewals.
• bill engagements (MSA + SOW).

One template library, one signature flow, one renewal cron. The executed PDFs live in pact and link back to whichever record asked for them.

Costs roll into tabs

Operational costs from across the suite show up in tabs with attribution:

• auto parts and labor on a repair order.
• ride fuel and maintenance per vehicle.
• rent property-level utilities and repairs.

You see your total spend by category, by vendor, and by the operational thing that caused it — not just by what hit the credit card.

bill closes the loop

bill is where money in lands. Service engagements, proposals, time entries, invoices, recurring billing, and client portal payments live in bill. Other apps can link or hand off billing context when a workflow needs money collected.