The questions that come before the first send

Three things: customers who agreed to hear from you, a sender the destination allows, and credit on the account.

Bring the customers in from a spreadsheet or add them by hand, write the message, and the review screen shows you the audience, the sender and the price before you confirm anything. See how audiences work.

No. Importing a list, writing a message, scheduling it and reading the results are all done in the app.

There is an API if you want to send from your own stack, but nothing about a campaign requires it.

Yes. Support is included with every account, at no charge, and it starts before your first send: setting up the account, choosing and registering a sender for the markets you want to reach, and getting the first campaign from a spreadsheet to the review screen.

Write to us before you sign up, or open the account and ask from inside the app.

That depends on where you are sending. Some markets let a message arrive from your business name the same afternoon; others require the name to be registered with the operators first, which takes as long as that regulator takes.

The board on the pricing page shows, for every destination, what the sender may be and whether it has to be registered first.

Yes. Import a spreadsheet, map its columns onto your own fields, and confirm what the file represents before a single customer record changes.

An import can never quietly hand you permission you did not have: anyone who has opted out stays opted out, whatever the file says. How consent is kept.

An SMS is billed in parts. In the standard alphabet one message holds up to 160 characters; past that it is split, and each part holds 153 so the phone can stitch them back together. In the wider alphabet the same numbers are 70 and 67.

The composer counts as you type and shows the number of parts before you send, so a message never quietly becomes two. Try it on a real message.

Yes, but some characters cost more room than others. A single one outside the standard alphabet moves the whole message into the wider one, and the number of characters it holds drops sharply.

The calculator names the exact characters that did it, so you can decide whether to keep them or swap them. Nothing about this is guesswork you have to do yourself.

Yes. Drop your own fields into the message and each one is filled in per record as the campaign is prepared.

That is also why the price is worked out against the real audience rather than an average: a longer name can push one customer's message into a second part while everybody else's stays in one. See the composer.

Yes. Preview it as an individual customer will receive it, personalization filled in, and send a test to yourself first.

The review step then puts the audience, the sender, the number of parts and the price on one screen, and nothing leaves until you approve it.

Both. A campaign can be scheduled for later, sent in batches rather than all at once, and paused and resumed while it runs.

Permission is checked again before each batch, so anyone who opted out after you scheduled is skipped rather than sent to.

Every recipient gets their own short link, so a click is attributable to one customer rather than to the campaign as a whole. The opt-out link works the same way.

Both are short by design: the message keeps the number of parts it had when you wrote it. What the click report holds.

In many markets, yes. Others allow only a short code, and some only an ordinary long number. Where a name is allowed it sometimes has to be registered with the operators before you may use it.

It is a per-destination rule, not a per-account one. The board on the pricing page shows what each market permits and which ones require registration first.

The rate board on the pricing page lists every destination the site quotes, with its rate and its sender rule, and it is searchable.

If you need a market that is not on it, tell us which one and we will tell you what would have to be ready first.

Yes, and sent and delivered are kept apart, because they are not the same claim. Each message carries its own result, and the recipient log holds one line per person.

The whole run can be exported when you need the detail somewhere else. See what reporting covers.

It is listed with the reason it failed, beside the rest of the run, so a bad number or a rejected sender is something you can see rather than something you infer from a total.

A message that fails before it leaves is not charged.

Not yet. SMS is the channel you can use in Messalogy today; WhatsApp sending is still being built.

The customer profiles, permissions and campaign history you build now are designed to carry over to it when it arrives.

Add an unsubscribe link while you are writing. Every recipient gets a secure link of their own, and their choice is recorded the moment they use it. Using the link again does not create a second change.

You decide where the link sits in the message, and you remain responsible for including it where the law requires it.

Not quietly. Rejoining takes a clear, recorded action. Importing the same person again, or restoring them from an earlier state, does not make them marketable by accident.

A bulk suppression can take permission away, but nothing bulk can create it.

Yes. Whether a customer can receive SMS, when that last changed and where the change came from are all kept with the customer, and the earlier decisions stay.

So the record reads as a history rather than a setting somebody last flipped. See how it is kept.

They are skipped. Permission is checked again before each part of the send rather than frozen at the moment you scheduled, so a campaign that goes out tomorrow reflects the choices people made today.

No. You buy credit and spend it on messages. There is no monthly platform fee and no charge per seat, so adding a colleague to the account costs nothing.

One balance is shared across your organization and its projects.

It depends on where it is going and how much room it takes. Both are published rather than quoted on request: the board on the pricing page carries the rate for every destination, and the calculator beside it prices a real message against one.

Yes, the rate comes down above a certain volume. What that means for you depends on where you send as well as how much, so it is a conversation rather than a table.

Tell us your monthly volume and your markets and we will explain the rates available to you.

By card or by wire transfer. For a transfer you get a pro-forma document your finance team can work from, and invoices are available in the app.

The messages that actually left. A message that fails before it leaves is not charged, and several campaigns running at once cannot spend the same credit twice.

Sending pauses. It does not push you over budget and it does not silently drop the rest of the audience, so you can top up and carry on.

Balance alerts are there to keep you from meeting that moment by surprise.

Because the estimate is made before the send and the charge after it. The review prices the real audience with the rates that apply to your account at that moment, and personalization can make one customer's message longer than another's.

The final charge then reflects the messages that successfully left.

Yes. /api/v1 covers transactional sending, contacts, lists, custom fields, segments and campaigns, with analytics at project, campaign, recipient and contact level. Sender IDs and your balance are readable.

See what it covers.

Yes. An API key can carry a webhook URL and a secret; events are signed with HMAC-SHA256, retried with dead-letter handling behind them, and applied idempotently, so a redelivered event does not corrupt your state.

Messages sent through the API also appear in the app, so support can see what a customer received without you building a viewer for it.

No, and the transactional path deliberately keeps out of it: it does not create marketing contacts and does not consult opt-out state. A passcode is not a promotion, and the two should not share a consent model.

That also means the legal basis for what you send there is yours, not ours.

Each key is scoped to a single project and can be restricted to an IP allowlist. Key status is checked on every call, so revoking one takes effect immediately.

A key inherits its project's isolation: contacts, segments and campaigns from another project are not reachable with it. Credit is organization-wide, so an integration and your campaigns spend the same balance.