One campaign builder for every channel and audience

Three types. Triggered campaigns fire when a customer action or database condition occurs: completing KYC, crossing a tenure threshold, or triggering a business rule. One-time campaigns are scheduled sends to an uploaded or curated audience: Excel files, CSVs, SFTP drops, or a cohort selected in the builder. Automated campaigns run on a recurring schedule or rule: for example, a cross-sell offer sent every week to customers who meet specific criteria. All three types run through the same consent validation and maker-checker approval workflow. Fyno handles them in one campaign builder without forcing one workflow onto the other.

Yes. Fyno Campaigns handles SMS, email, WhatsApp, push notification, and in-app channels from one campaign builder. You do not need separate tools per channel. Channel selection is driven by the campaign configuration or by each customer's channel preference stored in the preference manager. Fyno handles message bifurcation automatically: the same campaign content is adapted per channel template, and each channel's delivery, open, and click metrics are tracked independently. For BFSI operations where a single multi-channel campaign might reach millions of customers, Fyno's infrastructure handles banking-grade scale. Karnataka Grameen Bank processes approximately 3 million message requests per day across multiple channels and providers.

Fyno validates each individual message against the customer's current consent status at the moment of dispatch, not at the moment of segmentation. If a customer opts out of WhatsApp between the time a segment was built and the time the campaign fires, that customer's WhatsApp message is suppressed automatically. The suppression is applied at the routing layer in real time, before the message reaches any vendor. DND status is also checked against the TRAI registry before any promotional send. Every suppression event is logged with the reason and timestamp for regulatory audit purposes. This applies equally to dynamic campaigns from live cohorts and static campaigns from uploaded lists.

Fyno supports A/B testing at scale for any campaign type. You create message variants, define the subset size for the test audience, and Fyno sends each variant to its assigned group. After the test window, delivery rates, open rates, and click rates per variant are available in the campaign analytics dashboard. You select the winning variant and Fyno sends it to the remaining audience. The entire test-to-send cycle happens within the same campaign workflow without requiring a separate tool or manual data export. Approval and consent validation apply to both test sends and full sends equally.

Yes. Fyno supports Excel uploads, CSV files, and scheduled SFTP file drops as campaign sources for static campaigns. Scheduled uploads at defined times automatically populate campaign templates with data fields from the file: company name, loan number, EMI amount, bank account, and any custom attributes. API-based triggers and database events via Fyno Connect are also supported for dynamic campaigns. All trigger sources feed into the same consent validation and approval workflow, so that governance is consistent regardless of how the campaign is initiated.

Your existing campaign tool likely works from exported audience lists. You build a segment, export it, and the campaign tool sends from that snapshot. Two gaps follow for BFSI. First, customers who no longer qualify still receive the message because the list was frozen at export time. Second, consent is checked at segmentation, not at send. Most teams also manage triggered sends, bulk campaigns, and recurring automations across separate tools. Fyno consolidates all three campaign types into one builder with consent validated at every dispatch. You get triggered, one-time, and automated campaigns in one platform instead of managing separate tools for each.