Campaign objective, owner and audience
The information remains attached to the relevant customer, booking, payment, inventory or business record instead of becoming an isolated task.
Available · Sandesh
Plan customer email around a real audience and business moment.
A structured Sandesh workspace for preparing, reviewing, scheduling and measuring business email campaigns.
Campaign command centrePlan, publish and learn
Delivered10,55698.0%
Unique opens4,88045.3%
Link clicks1,61615.0%
CampaignStatusOpensClicks
Monsoon booking guideLive45.3%15.2%
Partner updateScheduled——
Repeat traveller campaignCompleted41.8%13.6%
Audience selectedContent approvedSend scheduled
The moment this becomes relevant
For teams whose campaigns live across documents, calendars and disconnected sending tools.
ISIKKO starts with the customer promise and follows it into the vendor's operation. The public experience, payment state, inventory decision and team action should describe the same commitment.
See the complete Sandesh solution →What the capability covers
A useful system is specific about the work it connects.
The released scope depends on merchant configuration, eligibility and the product status shown on this page.
Reusable content and campaign structure
The information remains attached to the relevant customer, booking, payment, inventory or business record instead of becoming an isolated task.
Review, scheduling and delivery controls
The information remains attached to the relevant customer, booking, payment, inventory or business record instead of becoming an isolated task.
Delivery, open and click reporting
The information remains attached to the relevant customer, booking, payment, inventory or business record instead of becoming an isolated task.
From first action to operating record
How the working flow comes together.
Each step leaves enough context for the next person or system to understand what has already happened.
- 01Objective and audience are selected
The next status is created only when the relevant business action is completed or verified.
- 02Message and assets are prepared
The next status is created only when the relevant business action is completed or verified.
- 03Compliance and links are reviewed
The next status is created only when the relevant business action is completed or verified.
- 04Campaign is scheduled
The next status is created only when the relevant business action is completed or verified.
- 05Results inform the next campaign
The next status is created only when the relevant business action is completed or verified.
Before implementation
Questions a serious buyer should ask.
A walkthrough should be grounded in your real locations, customer journey, inventory, payment process, roles and existing systems.
What must remain yours?
Your brand, customer relationship, pricing logic, policies and operating responsibilities need clear ownership.
What needs integration?
List the website, payment partner, accounting process, data source and team workflow that cannot be treated as an afterthought.
What proves success?
Choose measurable outcomes such as faster confirmation, fewer conflicts, clearer collections or less re-entry of information.
Buyer questions
Questions about email campaign planning and delivery
The answers below are visible to readers and represented by matching FAQ structured data.
Is Sandesh available now?
Yes. Sandesh is available for campaign creation, audience organisation, scheduling and performance monitoring. The enabled sending scope depends on the approved workspace and sender configuration.
Will it send every type of email?
Supported campaign and transactional use cases depend on the enabled channel, sender setup, consent, volume controls and applicable policies.
Will it support non-travel businesses?
Yes. Sandesh supports travel and broader business marketing workflows.
Who should consider Email campaign planning and delivery?
Email campaign planning and delivery is relevant when a sandesh buyer recognises the operating problem described on this page and wants the customer promise and vendor action to share one record.
What business outcome should Email campaign planning and delivery improve?
The implementation should improve a measurable handoff such as confirmation time, collection clarity, availability control, reporting effort or the amount of information re-entered by the team.
Can Email campaign planning and delivery fit an existing website or system?
The current stack is mapped before implementation. Where supported, ISIKKO can provide a customer journey, configured handoff, report or API rather than requiring an unnecessary replacement.
Can Email campaign planning and delivery be configured around our terminology?
Supported labels, fields and output structures can be mapped to the agreed business vocabulary while the underlying data model remains governed and consistent.
Does Email campaign planning and delivery work for more than one location?
The ISIKKO tenant model supports growing travel businesses with multiple locations, teams and services, subject to the configuration required by this capability.
Can our team use Email campaign planning and delivery from mobile and desktop devices?
Customer and vendor interfaces are designed responsively for supported phones, tablets, laptops and desktops. The exact view depends on the user's role and task.
How is access to Email campaign planning and delivery controlled?
Access is assigned to authorised organisations and roles so customers, vendor users and administrators see only the actions appropriate to the configured workflow.
What information must we provide before configuring Email campaign planning and delivery?
Bring the current process, responsible roles, service rules, data fields, exceptions, integrations and the measure that will prove the capability is useful.
Can information from Email campaign planning and delivery appear in reports?
Relevant events and statuses can become reportable data when the reporting module, permissions and definitions are configured.
How does Email campaign planning and delivery connect to the rest of ISIKKO?
The sandesh/email-campaigns capability is designed to share the relevant customer, booking, payment, inventory or business context so the next module does not begin with an empty record.
Can Email campaign planning and delivery be introduced in phases?
Yes. A scoped rollout can start with the highest-friction workflow, validate the operating model and expand after the team is confident in the data and responsibilities.
What happens when an exception occurs in Email campaign planning and delivery?
The workflow should preserve the status and context needed for an authorised person to act, rather than hiding the exception or treating it as a successful step.
Will Email campaign planning and delivery remove every manual task?
No. The objective is to automate repeatable handoffs and make necessary human decisions clearer, traceable and better informed.
How is implementation scope agreed for Email campaign planning and delivery?
A walkthrough maps the real customer journey, vendor operation, eligibility, integrations and constraints before the final configuration and delivery plan is documented.
How do we evaluate Email campaign planning and delivery after launch?
Compare the agreed measures before and after rollout, review exceptions with users and improve the configured flow instead of judging success by feature count alone.
Ready when your business is
Map email campaign planning and delivery to your real business flow.
Bring the current journey, systems and constraints. The useful next step is a scoped walkthrough—not a generic feature presentation.