Skip to main content

Marketing

Marketing is where your team plans campaigns, sends marketing email, runs automated journeys, publishes landing pages and forms, and scores leads for sales. Every contact carries a consent record per purpose, so you can show who agreed to what and when. When CRM and Books are on, contacts are shared with CRM and campaign return is measured on won deals and invoices.

Who uses it​

  • Marketing admin: sets up sender domains, the consent notice, tracking sites, scoring rules and approvals; handles suppression and erasure.
  • Marketer: builds lists, segments, emails, journeys, pages, forms, WhatsApp broadcasts, social posts and campaigns; reads reports. Email sends need an admin's approval when that setting is on.
  • Sales owner: receives qualified leads in CRM and follows up form leads from the mobile app.

Before you start​

  • Your company is set up in Thoshika and Marketing is switched on for it.
  • People who will use Marketing hold the Marketing admin or Marketer role.
  • You can add DNS records for the domain you will send email from.
  • You have your organisation's postal address and a privacy notice for marketing (what data you collect, for which purposes, how to withdraw, and a grievance contact).
  • Optional: CRM (shared contacts and lead hand-off), Books (campaign costs and invoiced revenue) and Bookings (webinars and demo scheduling).

Set up​

  1. Company settings. Enter your brand details (logo, colours, footer address) and the DPDP notice text and version. The notice link appears next to consent boxes on every form.
  2. Sender domain. Add your sending domain. Marketing shows the DKIM, MAIL FROM, SPF and suggested DMARC records to add at your DNS provider. Use the live check until the domain shows as verified; only verified domains can send.
  3. Senders. Add one or more from-addresses on the verified domain, with a reply-to address, and choose a default.
  4. Sending rules. Review the send window (IST days and hours), the hourly throttle, open and click tracking options, and whether email sends need approval.
  5. Topics. Set the email topics people can choose in the preference centre, such as newsletter, product updates and events.
  6. Import contacts. Upload a CSV, map the columns, choose how duplicates are handled, and record the consent basis: which purposes people agreed to, where, and a proof file. Contacts imported without consent are kept but cannot be emailed.
  7. Scoring. Adjust the fit and behaviour rules and the MQL threshold, and decide whether MQLs are handed to CRM automatically.
  8. Tracking (optional). Add your website as a tracking site and place the tracking script on it. Choose whether visitors must accept tracking first.

Key workflows​

Send an email campaign​

  1. Create a campaign with a code, dates and budget, so emails, pages and costs are grouped together.
  2. Build the email from blocks or a template. Add merge tags and, if needed, show blocks only to certain contacts.
  3. Choose lists and segments to include and exclude. The audience preview shows how many people are removed for missing consent, suppression or opting out of the topic.
  4. Optionally set up an A/B test on subject, content or sender.
  5. Run the pre-send checks, send a test, then schedule. If approval is required, the email waits in the admin's inbox.
  6. After sending, read the report: delivered, opens, clicks, unsubscribes, bounces and complaints.

Build an automation journey​

  1. Start from a recipe (welcome series, webinar follow-up, nurture, re-engagement or MQL hand-off) or a blank journey.
  2. Pick the trigger, for example a form submission, a booking, or a contact entering a segment.
  3. Add delays, if/else branches and actions such as sending an email, updating the contact or creating a CRM lead.
  4. Set a goal and the re-entry rule, then activate. Watch the per-step counts to see where contacts wait or leave.

Capture leads with a landing page and form​

  1. Create a form with the fields you need, one unticked consent box per purpose, and optional double opt-in.
  2. Build a landing page and place the form on it, or embed the form on your own site inline, as a pop-up or as a floating button.
  3. Choose what happens on submit: a thank-you message, a redirect, or a Bookings scheduler so the visitor can book a call straight away.
  4. Submissions create or update contacts, record consent and UTM source, and can start journeys or create CRM leads.

Prepare a WhatsApp broadcast​

  1. Draft a template with its Meta category, language and variables; Marketing checks it against Meta's limits.
  2. Choose the audience. Only contacts with WhatsApp marketing consent and a valid Indian mobile number are eligible.
  3. Export the list in WATI, Interakt or generic CSV format and send it from your WhatsApp Business tool.
  4. Import the delivery report afterwards to fill in the broadcast statistics.

India specifics​

  • Consent is recorded per purpose (email, WhatsApp, SMS, tracking) with notice version, source and time, in line with the DPDP Act 2023. Withdrawal is as easy as giving consent.
  • Forms can require an age confirmation so that marketing consent is not recorded for children.
  • SMS exports carry your TRAI DLT entity ID, sender header and template IDs for upload to a DLT-registered provider.
  • Send windows run in IST; mobile numbers are validated as +91; forms offer Indian states; reports follow the April to March financial year.

Works with other apps​

  • CRM: shared leads and contacts, MQL hand-off, deal stages as triggers and won deals for attribution.
  • Books: campaign costs from Books expenses and bills tagged with the campaign code; invoiced revenue for ROI.
  • Bookings: webinar registrations, demo scheduling on thank-you pages, and bookings as journey triggers.
  • Sangam: journey notifications posted to a channel.
  • The mobile app shows campaign stats, approvals and new form leads with call and WhatsApp follow-up.

Next steps​