Internal communications system

WCAP Messages

What started as a shared customer-text inbox grew into the internal communications layer our team uses across two businesses. Each workspace keeps its own number, customers, messages, campaigns, and calls while authorized operators can switch businesses without mixing data or caller identity.

Built and operated by the same operators behind WCAP Works.

Why it matters

Custom software should fit the operation, not force the operation to fit the software.

Local service businesses often end up with customer texts, calls, staff handoffs, campaigns, and business numbers spread across separate tools. WCAP Messages shows how a focused internal system can connect those workflows while preserving the infrastructure that already works.

Type

Internal operations software

Industry

Multi-business local service operations

Scope

Multi-workspace communications, Shared SMS/MMS inboxes, Outbound calling, SMS campaign workflows, iPhone companion, Push notifications, Operator access controls

Status

Operating internal system

One team. Multiple businesses. Different customer identities.

The original problem was shared texting. WCAP Detailing and WCAP Works each have their own customers, business number, communication history, and staff access. Authorized operators need to move between those businesses without mixing customer records, sender identity, or caller ID.

One app, isolated workspaces.

WCAP Messages treats each business as its own workspace. Operators see only the businesses they belong to, and the active workspace sets the public identity used for messages and outbound calls. Detailing conversations stay with Detailing. Works conversations stay with Works.

Messaging became an operating workflow.

Shared SMS and MMS conversations include attachments, unread state, delivery feedback, search, notifications, and new conversations. Campaign tooling adds recipient imports, review and approval, test sends, suppression handling, and a controlled send. Bulk messaging is not an open blast button.

Calling without replacing the phone system.

Outbound calls start from the customer conversation and show the active business number. The system supports native iPhone calling plus browser and cellular paths, keeps call history and quality diagnostics, and leaves each business's existing inbound voice routing in place.

WCAP Messages on two phones: the workspace switcher with WCAP Works selected, and an active WCAP Works conversation with calling and attachments.
One internal system, separate business workspaces. Authorized operators can move between WCAP Detailing and WCAP Works while the active workspace keeps its own customer and phone identity.
WCAP Messages inbox with the workspace menu open, WCAP Works selected beside WCAP Detailing, and All and Unread filters.
The workspace switcher keeps WCAP Detailing and WCAP Works inside one operator app without combining their conversations.
WCAP Messages conversation for WCAP Works showing an outbound message, operator attribution, Delivered status, a call button, thread controls, and an attachment composer.
An active Works thread shows operator attribution, delivery state, attachments, and the call path directly from the customer conversation.
WCAP Messages settings showing notifications on and Home Screen installation complete, with the account email blank.
Settings keep notification and Home Screen status visible. The account email is blank in this capture.
WCAP Messages push notification announcing a new message from Tester.
A notification from a supplied test exchange. On iPhone, push requires Home Screen installation and notification permission.

What was built

What was built.

A multi-workspace system for WCAP Detailing and WCAP Works, with separate conversations, messages, campaigns, and calls

Shared SMS and MMS inboxes with attachments, search, unread state, and delivery feedback

A business number and outbound caller identity for each workspace

Access for owners, admins, salespeople, and team members, limited to the businesses they belong to

Push notifications and iPhone Home Screen support for messaging

SMS campaign workflows with import, review, approval, test sends, and suppression safeguards

Outbound calling from the customer conversation, through native iPhone, browser, and cellular paths, with call history and quality diagnostics

Server-controlled sender and caller identity, plus opt-out handling and safeguards against duplicate sends or calls

What it shows

What it proves.

WCAP Messages started with a narrow operational problem and expanded only as real needs appeared. It shows our approach to custom business software: understand the workflow, isolate the right data, integrate with existing providers, put guardrails around risky actions, and keep the day-to-day interface simple for the people using it.

Messaging is an iPhone-first web app with push notifications. Outbound calling adds a native iPhone companion, plus browser and cellular paths. The app is Next.js and TypeScript on Neon Postgres. Twilio carries the messages and outbound calls, and the server decides workspace access and which business number the customer sees.

Built and operated by WCAP for its own businesses. Presented as internal software and systems proof, not client work, a public software subscription, or a measured performance claim.

Start with a free Website & Google Check.

We will look at how the business appears online and show you the biggest things we would fix first.

Prefer to talk first? Call +1 (902) 706-8171 or send a text.