FAQ & troubleshooting
Quick answers to common questions about sending, billing, and switching to Peleka.
General
No. Every new workspace starts with a free trial (500 contacts and 500 email sends) with no credit card required. See Subscription & billing.
Yes. Broadcasts, automations, forms, and segments all work without a connected store. You'll just miss out on purchase-based triggers, revenue analytics, and the auto-generated smart segments until you connect one. See Connecting your store.
Sending and publishing are gated behind the quickstart checklist: verified email, a physical address, an authenticated sending domain, and a sender identity. Drafting doesn't require any of this; only going live does.
A tag is a simple label you apply manually or via automation. A segment is a saved filter: static (a fixed set you curate) or dynamic (rule-based, updating automatically as contacts' data changes). See Segments, tags & fields.
Yes. Peleka has a built-in MCP server for exactly this. See Connect Peleka to an AI assistant.
Deliverability issues
First, check your sending domain's status: a DNS regression (someone removed a DKIM record, a registrar migration reset your zone) is the most common cause, and Peleka's weekly health check will have flagged it if so. Next, check whether your domain's warmup got auto-paused due to bounce or complaint rate; see the callout in Sender profiles & deliverability.
Open the broadcast's report to see the failure reason, fix the underlying cause (often a domain or list-quality issue), then use Retry Send from the row's ⋯ menu. Peleka only re-attempts the recipients that actually failed, not your whole audience again.
Bounces and manual suppressions, yes: from the Suppressed tab in Audience. Spam-complaint suppressions can only be removed by Peleka; contact support@peleka.io.
Every new domain goes through an automated risk check in parallel with DNS verification. If DNS finishes first, sending is paused pending a quick manual review, usually resolved within one business day. See Verifying a sending domain.
Billing
No. Subscription plans price by contact count and include effectively unlimited sending (a background fair-use cap exists around 100× your contact limit per month, high enough that normal use never approaches it). If you'd rather pay strictly per email instead, switch to Pay-As-You-Go credits.
Sending pauses with a "Payment past due" error until it's resolved. Update your card under Settings → Plans & Billing → Payment Methods.
They're forfeited. Peleka warns you before confirming the switch either direction (credits → subscription or subscription → credits).
Your plan stays active through the end of the current billing period. After that, your account reverts to the free tier and sending pauses until you reactivate or add Pay-As-You-Go credits.
Switching from another platform
Peleka doesn't use a "lists" model: import your contacts once and organize them with tags and segments instead (see Importing contacts). If you're connected to Shopify or WooCommerce, connect it in Peleka too rather than re-importing manually. The integration will sync customers, orders, and consent automatically and build the same kind of purchase-based segments you may be used to.
Yes, but answering "Yes, regularly" when adding the domain gets you onto the fastest available warmup track, well ahead of what a brand-new domain gets. See Verifying a sending domain.
There's no automatic importer for another platform's automations, so you'll rebuild them on Peleka's canvas. See Building a journey and Triggers & actions for the full building blocks available.
Still stuck?
Email support@peleka.io. Include your workspace name and, if it's about a specific send, the broadcast or automation name so support can look it up quickly.