KMail

KMail ยท Governed pharmacy communications

Got something to send? KMail gets it to the right person.

KMail keeps campaign decisions, configured communication and delivery context together while pharmacy staff retain the professional decisions that belong to them.

KMail exclusively owns campaign behaviour: audiences, exclusions, templates, approval, scheduling, automation, dispatch, delivery outcomes, feedback and coupons.

The pharmacy problem

Sending the right message takes control.

Campaign communications need the right people, the right scope and a clear record of what was approved before anything is sent.

What KMail does

What KMail handles.

The grouped work separates recipient selection, preparation and delivery so the campaign decision remains clear from start to finish.

Illustrative pilot workflow

From audience to delivery.

This static sequence explains the campaign path without creating a recipient, message, campaign record or delivery state.

  1. Set the audience and exclusions

    KMail frames who should receive a campaign and who is excluded before the communication is prepared.

  2. Prepare the communication

    Templates, coupons and configured SMS, email or portal communication form the proposed campaign composition.

  3. Approve and schedule

    The proposed communication receives visible approval and scheduling before dispatch is considered.

  4. Dispatch through Inbox

    KMail uses Inbox as its communications execution layer. Inbox provides underlying communications delivery foundations.

  5. Review delivery outcomes and feedback

    KMail retains traceable delivery outcomes and feedback in the campaign context after dispatch.

This is an illustrative pilot workflow, not a live product demonstration.

Staff control

Your team approves every send.

KMail supports preparation and traceability, while pharmacy staff decide what is approved and what may be shared.

Buyer value

Send with less guesswork.

KMail describes controlled selection, visible approval and delivery context so staff can understand the campaign path before anything is sent.

KSuite connections

How KMail connects.

Inbox supports the KMail dispatch path as a delivery foundation, while KMail remains the owner of campaign behaviour and communications context.

Illustrative scenario

A pharmacy update, ready to send.

The pharmacy defines the audience and exclusions, prepares the communication from approved material, confirms the review and scheduling path, then follows the delivery context after dispatch.

Pilot scope

Set the communication rules together.

KMail pilot communications functions, integrations and operating boundaries are agreed with the participating pharmacy before use.

Buyer questions

Questions about KMail.

These answers keep KMail campaign ownership, Inbox delivery foundations and staff review distinct.

What does KMail own?
KMail exclusively owns campaign behaviour: audiences, exclusions, templates, approval, scheduling, automation, dispatch, delivery outcomes, feedback and coupons.
What is the role of Inbox?
Inbox provides underlying communications delivery foundations. KMail uses Inbox as its communications execution layer; Inbox does not own KMail campaign behaviour. KMail does not currently organise or categorise the pharmacy inbox.