Everything a medical conference needs, from first abstract to final certificate.

What it does: maintains a reusable, org-wide Faculty directory, then lets an organizer Add, Attach, and Invite each faculty member as three independently-triggerable actions instead of one fused invite step.

Who it's for: organizers building a speaker roster across multiple events, and the program coordinator following up on who's actually confirmed.

How it works: Add places a person into a chosen group or, if none is picked, the org's default group automatically — never mandatory at add time. Attach creates their assignment for a specific event, either one person at a time via a search-as-you-type picker showing name and designation, or an entire group at once. Invite sends the confirmation email — attach and invite can happen together in one step, or separately, whenever it fits. The event's faculty roster shows every attached person, including anyone not yet invited or confirmed, with a visual hint distinguishing them from confirmed faculty at a glance. Each directory entry can also carry a photo, cropped and brightness-adjusted in a basic in-browser editor at upload time.

What it does: calculates each delegate's CME credit hours from actual attendance and auto-issues their certificate once the event closes — not a printable “certificate of participation” handed out regardless of what anyone attended.

Who it's for: societies whose delegates need documented CME hours for a licensing or accreditation body, and the organizers who'd otherwise be reconciling attendance sheets by hand afterward.

How it works: two ways a delegate's attendance gets recorded — Medvento is explicit about which one wins:

1. Per-session QR self-check-in — delegates scan a session-specific code as they enter; Medvento tallies the real hours attended.
2. Event-level check-in — organizer or staff mark a delegate attended for the whole event, used only as a fallback.

Per-session data always wins when it exists — scan three of five sessions, get credit for three. Event-level check-in only fills in when a delegate has zero session scans, crediting the event's full configured hours. Neither one on record, and no certificate issues — Medvento won't fabricate a credit nobody can substantiate.

What it does: an online submission form paired with an actual reviewer decision workflow — not just a place to upload a PDF and hope someone reads it.

Who it's for: the scientific or program committee chair running a call for papers, and the single reviewer each abstract gets assigned to.

How it works: the organizer opens a submission window with its own open date and deadline, set independently of the registration deadline. Authors submit online; the organizer assigns each abstract to one reviewer, who accepts or rejects it — that decision is final, with no numeric scoring layer to average and no separate organizer sign-off second-guessing the reviewer. Submissions lock automatically once the deadline passes; to let one late author in anyway, the organizer grants that as a per-submission exception, not by reopening the window for everyone.

What it does: Razorpay-native checkout with a registration record tracked from the moment checkout starts, not just the moment it succeeds.

Who it's for: the registration desk — the team who has to answer “I paid, why didn't I get a confirmation?” after the fact.

How it works: a delegate starts checkout and Medvento creates their registration record immediately, marked pending — mirroring Razorpay's own order/payment split. Razorpay's webhook confirms the payment and the record flips to confirmed automatically. If the payment fails, or the delegate closes the tab halfway through, the attempt stays visible as failed rather than disappearing — so the front desk can actually look up what happened instead of guessing. A GST-compliant invoice generates per registration.

What it does: composes and sends a mass campaign — Email or WhatsApp — to a Faculty group/contacts or an Attendee list, with a live preview and a test send before any real spend.

Who it's for: organizers reaching faculty or delegates at scale, without re-typing a recipient list for every event.

How it works: choose the channel, then an event, then recipients — Faculty (whole groups and/or individually-selected contacts) or Attendee lists, a mutually exclusive choice per campaign, never both combined. WhatsApp offers only admin-curated, Meta-pre-approved templates from the Meta Cloud API, each exposing its own typed parameters; Email is composed in an org-built drag-and-drop designer with dynamic-field insertion and a color-scheme chooser. A test send goes to one address or number you control before committing to the real one. At send time, price is the platform admin's currently active per-recipient rate for that channel, paid via Razorpay — tracked entirely separately from subscription billing. Confirmed campaigns send through a background job queue with no recipient-count ceiling, and every campaign — draft, sent, or failed — stays in a full send history afterward.

What it does: a template-based, block-library page editor an organizer assembles into a live event page themselves — no separate web developer, no waiting on one.

Who it's for: the organizer who needs a branded event page fast, without a design or development resource on hand.

How it works: pick a template, then arrange a constrained set of content blocks, set the event's own logo and color palette, and place a registration-form block wherever it belongs on the page — wired directly into the platform's real registration and payment flow, not a separate form bolted on afterward. Publishing revalidates only that page's own path, not the whole site, so a change goes live without a wait.

What it does: clones a prior event's structure — sessions, faculty list, and registration tiers — into a new edition, instead of rebuilding it from scratch.

Who it's for: a society running the same conference edition after edition, and the organizer who'd otherwise recreate last year's setup by hand each time.

How it works: pick a past event belonging to your org and clone it. A new event is created with that source event's sessions, faculty list, and registration tiers already in place — ready to configure for the new edition rather than starting from a blank form.