Sending & deliverability is where you prepare your channels: verify your email domain's DNS (SPF/DKIM/DMARC), record your US SMS brand registration, and connect a mailbox. Everything here is safe preparation. A channel only sends once fully configured, and nothing is sent on your behalf before then.
How do I verify my sending domain, and what does it do today?
- Open Settings → Sending & deliverability and add your domain.
- Finocket generates the exact SPF, DKIM and DMARC records to publish.
- Add them at your DNS provider (GoDaddy, Cloudflare, wherever your domain lives), then tap Re-check DNS.
- When all three verify, your domain is marked ready.
Today, campaign email sends from Finocket's shared sender, and verifying your domain does not change the From address yet. Verification puts you at the front of the queue for the dedicated-sending rollout, so the day it ships your mail moves to your own domain with zero downtime. One guard is live now: if you've started a domain but not finished verifying, outreach email is held so nothing goes out half-configured.
How do I see whether my email is landing?
Open Settings → Sending & deliverability → Deliverability. It shows, for your workspace, your sending domain and your mailbox:
- Spam complaints and hard bounces over the last 7 and 30 days. Gmail asks senders to stay under 0.10% complaints and never reach 0.30%.
- An automatic pause. If complaints reach 0.10% or hard bounces reach 3%, sending pauses and the screen says why. A pause on one domain or mailbox holds marketing only, and lifts by itself once the rate falls well below the line. A pause on the whole workspace holds every email Finocket queues for you until a Finocket operator resumes it, once the cause is fixed.
- Mailbox limits. Mail from your own Google Workspace mailbox stays under Google's 2,000 a day, and from Microsoft 365 under 30 a minute. You can set a lower daily limit, or a warm-up start date so a new mailbox begins at 20 a day and builds up over three weeks.
- Domain health. Your SPF, DKIM and DMARC records and two domain blocklists, checked every night or when you tap Check now. A check that could not get an answer says “Unknown”, never “Pass”.
If your mail goes out over SMTP (an app password), your mailbox does not report bounces or complaints back, so the screen says Not measured rather than showing a clean record.
In Campaigns, a draft campaign has two switches: Plain text sends it without formatting, and Track opens and clicks can be turned off. Plain text always goes untracked. The Unsubscribe button Gmail and Yahoo show beside your email works in one tap.
What is A2P 10DLC and do I need it?
Only if you send SMS to US numbers. US carriers require businesses to register their brand and campaign (A2P 10DLC) before application-to-person SMS is delivered reliably. Record your brand details here; SMS to the US stays queued until a provider is configured and the registration is approved. For US numbers the legal night window is enforced, not just configured. Each SMS is checked against the recipient's state and their own local time before sending (including the stricter Florida, Oklahoma and Washington windows), and out-of-window messages are held, never fired at midnight. If we cannot work out a US recipient's local time, the message is held rather than sent on an assumption.
What about Indian SMS (DLT)?
India's equivalent gate is TRAI's DLT system: a registered sender ID and per-message template IDs, entered with your SMS provider key under Outreach sending. Until they're in place, Indian SMS stays queued rather than being sent unregistered. Carriers filter unregistered traffic anyway, so this protects your delivery rate.
The night-hours check described above is a US rule, and Finocket applies it to US numbers only. TRAI also restricts promotional SMS at night in India, but that restriction is enforced through the DLT chain (your registered sender and the carrier), not inside Finocket. Treat the timing of your Indian promotional SMS as your own call.
When is marketing email allowed to leave?
Inside your workspace's sending hours, 8am to 9pm by default. A campaign, a follow-up ladder step or a one-off promotional email that comes due outside those hours is held and goes out when the window reopens.
This one is a courtesy, not a legal rule. No law sets night hours for email. India's TRAI rules cover calls and SMS, and the US CAN-SPAM Act sets no time limit at all. It is your own statement of when your customers should hear from you, so it is read on your workspace's clock (Indian time unless your workspace says otherwise) rather than each customer's. We do not know what time it is where your customer is sitting, and would rather tell you whose clock we used than guess.
Nothing transactional is ever held. Payment reminders, receipts, statements and your accountant's bulk reminder run go out whatever the hour, because a receipt at 10pm is still a receipt. A campaign recipient held for the hour is not counted as done. They stay pending, so your next send picks them up.
Why did an invoice or reminder say it couldn't be sent?
Because the address you were sending to is on a domain that cannot receive mail at all. Before anything leaves, Finocket asks the internet's address book whether the part after the @ accepts email. If the answer is a definite no (the domain does not exist, or it exists and publishes no mail server), the send stops and tells you, instead of going out and bouncing.
Too many bounced emails and the mail providers start treating everything sent from Finocket as suspicious, so one customer's typo can push another customer's invoice into a spam folder. Stopping the send protects those other invoices.
What to do: check the address on the client's record for a typo. A missing letter in the domain is the usual cause. Fix it and send again. If you are certain the address is right, send it once more in a few minutes; a temporary network fault never blocks a send, only a definite answer does.
An address that has bounced, or whose owner marked your mail as spam, is blocked separately and permanently. See Outreach & consent.
Can I connect my Gmail or Outlook?
Yes, connect via OAuth (sending from the connected mailbox is coming). Tokens are encrypted and Finocket never sees your password. If a provider isn't configured on your deployment, the button says “not configured” instead of pretending it's ready.
Related: Outreach & consent, Bring your own outreach keys.