MessageWiz

Two channels, one truth. SMS lives in Twilio. Email lives in SendGrid. Replies live nowhere.

SMS and email don't normally share a CRM. SMS lives in Twilio's console; email lives in SendGrid; the contact list lives in a Google Sheet, and reply-handling lives nowhere, replies arrive on the founder's personal phone and in the team's shared inbox at the same time, often hours apart, often not connected to a campaign at all.

MessageWiz's brief was to put both channels on one platform, with a unified contact record, one outbound composer, one inbox for replies, and analytics that compare SMS open rate vs. email open rate on the same campaign.

Buy a number in three clicks. Map a CSV to contact fields without writing JSON. Schedule and track everything from one screen, that was the brief, end to end.

A single pane for both channels. "Anything broken?", answered before the first coffee.

The dashboard is the operator's morning view, what went out, what came back, what's still in the queue. SMS and email metrics sit on the same row, color-coded but never separated. The active campaigns block lists everything in flight with delivery and open rates updating live.

The inbox preview shows the most recent unread replies, regardless of which channel they came in on. The founder's morning question is: "Anything broken?" The dashboard answers it before they finish their coffee.

A CRM that never asks you to write JSON. Drop a CSV. Map the headers. Send.

Importing contacts is the screen most messaging tools botch. We didn't. Drop a CSV; MessageWiz reads the headers, suggests field mappings, flags duplicates against existing contacts, and shows a live preview of the first five rows with the mapping applied.

Custom fields get created on the fly. The contact table itself is built for two-channel triage, every row carries last-message-out, last-reply-in, channel preference, and tags, with inline chat panel on click so the operator can reply to any contact without navigating away.

Replies arrive in one inbox. SMS and email, threaded by contact, switch channel mid-conversation.

The inbox is the most visited screen in the product. Every inbound SMS and email lands here, threaded against the contact who sent it, color-tagged by channel. The operator can reply in either channel from the same composer, switching from SMS to email mid-conversation without losing context. Filters scope to unread, awaiting-reply, by-tag, or by-campaign.

The metric we track most: median time-to-reply. Before MessageWiz it was untracked entirely, replies leaked across personal phones and shared inboxes. Now every conversation is timestamped end-to-end.

Write once, send to whichever channel converts. The message is the asset, not the channel.

The composer treats the message as the asset, not the channel. Write a body; preview it as SMS (140-char chunked) and as email (subject + HTML rendered) side by side; pick the audience segment; schedule or send.

Drafts persist until the team is ready to ship them, with comments and approval status when the founder isn't the only sender. {first_name}, {company}, and any custom field plug into either channel without re-mapping.

Sequences without a sequence builder degree. A vertical script, trigger, step, branch, not a Visio diagram.

Every messaging tool has an automation builder; most look like Visio. Ours is a vertical list, trigger → step → step → end, with branch logic exposed as inline if/else, not a separate canvas.

Triggers cover the obvious ones (new contact, tag added, replied "STOP," didn't open after 3 days). Steps cover SMS, email, wait, branch, tag. The whole automation lives in one scrollable column and reads like a script.