CRM & outreachUpdated 29 Aug 2026

Bring your own outreach keys (Email, WhatsApp, SMS)

Send on your own Email, WhatsApp and SMS provider accounts (or straight from your own mailbox with an app password), with keys encrypted per workspace and never shown again, company keys applying to everyone while personal keys override them, and the consent chokepoint unchanged.

Finocket sends outreach on its own included accounts out of the box, with nothing to set up. If you'd rather send from your own provider accounts (your sender identity, your reputation, your provider bill), add your keys under Outreach sending, which Settings → Connected keys links to (it is not a settings row of its own). Consent checks are unchanged either way.

Which providers are ready today?

  • Email (ready): Resend and ZeptoMail. Each needs an API key/token and a verified from sender or domain at the provider.
  • Your own mailbox over SMTP (ready): send straight from the address you already use, with no email-provider account and no domain to verify. You need your mail server (Gmail and Workspace use smtp.gmail.com on port 465), your address, and an app password. Your normal password will not work. Google issues one under Security → App passwords, and only after 2-Step Verification is on. Finocket makes a real connection and logs in before saving, so a wrong password is caught on the form rather than when a customer doesn't get an email.
  • What sending from your own mailbox costs you: your mailbox can't tell Finocket when a message bounces or when someone marks it as spam. The safeguard that pauses sending after a spike in complaints therefore has nothing to watch on this route, so an empty warnings screen means it isn't being measured, not that nothing is wrong. Mailbox providers also cap you: Gmail and Workspace stop somewhere around 2,000 recipients a day. Good for reminders, statements and low-volume follow-ups; use a dedicated email provider for a large campaign.
  • Email (listed but coming soon): Amazon SES and SendGrid appear in the list, but they are not wired yet. You can't rely on them for sending today; use Resend, ZeptoMail, your own mailbox, or the included sender.
  • WhatsApp (ready): Meta Cloud API (phone-number ID + permanent access token) and 360dialog (API key). Business-initiated messages must use a Meta-approved template.
  • SMS (ready): MSG91, Fast2SMS, Twilio and Plivo. Indian routes need a DLT-registered sender ID and template IDs; US routes on Twilio need approved A2P 10DLC registration. Until those are in place, SMS stays queued and is never fired unregistered.

What's the difference between a company key and a personal key?

A company credential, which only the workspace owner can set, applies to everyone in the workspace. A personal credential, which any member can set, overrides the company one for that member's own sending. Set neither and Finocket's included sending applies. This lets a business run one official sender while a field salesperson sends from their own account.

What does bringing a key change, and what doesn't it?

A key only swaps the transport: the account a message physically leaves from. Everything that decides whether a message may go (consent, suppression, quiet hours, template class, jurisdiction rules) runs exactly as before through the single send checkpoint. Your own key never bypasses compliance.

How are my keys protected?

Every credential is encrypted per workspace before it's stored. Plaintext never lands in the database, and a saved key is never shown again. The screen only shows which provider is configured and whether it's verified. To rotate a key, paste a new one over it. When you save, use Save & send test email (email) or Save & verify (WhatsApp/SMS). Only verified credentials are used for real outreach, so a bad key can't silently swallow a campaign.

Related: Email, campaigns and consent, Sending & deliverability.

Does this work offline?

Frequently asked questions

Does Finocket track what my email and SMS sends cost?

Yes, once you tell it your rates. Finocket ships no price list, because email and SMS rates differ by provider, by route and by whatever volume you negotiated, and a guessed number on a cost screen is worse than no number. Enter your per-send email rate and your per-segment SMS rate, and every send is recorded with its cost. Until you do, the cost reads as unknown rather than as zero.

Why is my SMS priced per segment instead of per message?

Because that is how carriers bill it. A plain English SMS fits 160 characters in one segment. A single character outside the basic GSM alphabet (any Hindi, Kannada, Tamil or Telugu letter, and most emoji) switches the whole message to a different encoding where only 70 fit, and long messages lose a few more characters per segment to the joining header. So the same 71-character message is one segment in English and two in Hindi. Finocket counts the segments the way the carrier will, so a message in your own language is not quietly under-costed.

How much does the WhatsApp Business API cost in India?

Meta charges per conversation, with rates varying by category (marketing conversations cost more than utility ones); BSPs like 360dialog add their own plans. With Finocket you bring your own Meta Cloud API or 360dialog account, so you pay the provider directly at their published rates, with no markup.

Do I have to bring my own keys to send campaigns?

No. Finocket's included sending works with zero setup. Bring keys only when you want your own sender identity and deliverability reputation, or your own provider pricing. If a channel has no key, the included transport is used automatically for that channel.

Why is my SMS sitting in 'queued'?

Indian SMS needs your DLT sender ID and template registered; US SMS on Twilio needs approved A2P 10DLC. Until those are configured, Finocket holds the messages as queued rather than sending unregistered traffic that carriers would filter or fine. Complete the registration and queued messages become sendable.

Can I store an Amazon SES or SendGrid key now?

You can save the key, but these two adapters aren't live yet. Sending stays on your active provider (or the included sender) until they're enabled. For your own email sending today, use Resend, ZeptoMail, or your own mailbox over SMTP.

Can I just send from my own Gmail or Workspace mailbox?

Yes. Choose 'Your own mailbox (SMTP)' and enter your address, your mail server and an app password. Your normal password will not work: Google requires 2-Step Verification on the account first, and then issues a separate 16-character app password under Security → App passwords. Finocket makes a real connection and logs in before saving, so a wrong password is caught while you are still on the form rather than when a customer does not get an email.

What is the catch with sending from my own mailbox?

Two things, and both matter more as volume grows. Your mailbox cannot tell Finocket when a message bounces or when someone marks it as spam, so the safeguard that pauses sending after a spike in complaints has nothing to watch on this route. An empty warnings screen means it is not being measured, not that nothing is wrong. And mailbox providers cap sending: Gmail and Workspace stop you somewhere around 2,000 recipients a day. It is a good fit for reminders, statements and low-volume follow-ups, and the wrong fit for a large campaign; use a dedicated email provider for that.

Can my accountant see or change the keys?

No. Accountants are read-only across the workspace and never see credentials. Nobody does after saving, since only the provider name and verified status are displayed. Company keys are owner-only to set; team members can only manage their own personal keys.

Does using my own WhatsApp number let me skip template approval?

No. Any business-initiated WhatsApp message through the official API must use a template Meta has approved, whichever account it sends from. Finocket won't attempt an unapproved template send, which protects your number from being flagged or banned.

Related articles