Skip to content

Features

Everything a calling team needs, and nothing it has to work around.

Swastik CRM does fewer things than a general CRM, on purpose. Each one is here because a lead slipped through without it.

01

The call loop

One sheet does the work of a call log, a status update and a calendar entry. The goal is three interactions from tapping Call to a saved outcome with the next follow-up booked.

  • Call, WhatsApp and Email on every lead, through tel:, wa.me and mailto: links.
  • Tapping Call opens the log-outcome sheet straight away, with a timer running for the call duration.
  • Disposition chips, an optional note, and next follow-up quick picks: 15 minutes, 1 hour, 3 hours, tomorrow 10:00, next week, or a custom time.
  • Dispositions are yours to define. Each can carry a default next follow-up (No answer → +2 h), a stage to move to, and whether it counts as connected.
  • Saving writes the call, the status changes and the new follow-up together, so the record is never half updated.

02

Follow-up alerts

Follow-ups are the product. When one is due, the agent is interrupted, and if they stay silent, their manager is told.

  • A follow-up is a lead, an owner, a due time, a type (call, meeting, WhatsApp, email or task) and a note. A lead can have several.
  • An optional pre-alert before the due time, then the main alert, delivered to every tab the agent has open, within seconds of the due time.
  • A toast with name, phone and note, and Call, Snooze (5 min, 15 min, 1 h), Done and Open buttons.
  • Four synthesised tones with volume control. The sound repeats every 30 seconds until the agent acts.
  • A desktop notification when the tab is hidden, and a flashing tab title.
  • After the organisation’s escalation window (15 minutes by default), the follow-up turns overdue and the team manager or reporting manager is alerted.
  • A notification centre with an unread count, a daily agenda of overdue, today and upcoming, and quiet hours per person.

03

Focus mode

For agents working a list all day: one lead on screen at a time, in the order that matters.

  • The queue runs overdue first, then due, then upcoming, then leads that have never been called.
  • Call, log the outcome, and the next lead appears. No searching, no choosing.

04

Multi-level lead details and stage gates

Lead data grows as the deal does. Swastik CRM lets you structure it in levels and insist on the right fields before a lead moves on.

  • Core fields on every lead: name, phone (normalised to international format), alternate phone, email, company, city, source, value and currency, priority, temperature, tags, owner, team, pipeline and stage.
  • Custom fields grouped into ordered sections such as 1 · Contact, 2 · Qualification, 3 · Proposal, 4 · Closure.
  • Twelve field types: text, long text, number, currency, date, date and time, select, multi-select, checkbox, phone, email and URL.
  • Stages can require fields. Moving a lead into such a stage opens exactly the missing fields; it moves once they are filled.
  • Duplicate detection on phone and email when a lead is created or imported.

05

Five statuses, tracked separately

Stage, last call disposition, priority, temperature and follow-up state each answer a different question, so Swastik CRM keeps them apart.

  • Filter and sort by any combination: hot leads in Qualified whose last call was No answer and whose follow-up is overdue.
  • Every change of any status is written to the lead’s timeline with who changed it, when, and from what to what.

06

Pipelines and the board

Run admissions and corporate sales side by side without mixing them up.

  • Several pipelines per organisation, each with its own stages marked open, won or lost, and a colour.
  • A drag-and-drop board per pipeline. Stage gates apply on the board too.
  • Bulk actions: assign, move stage, set priority, add or remove tags, delete. Admins can restore deleted leads.

07

Roles, teams and sharing

Roles say what a person may do. Relationships say which leads they may see. Together they cover branches, partners and reporting lines without a role per edge case.

  • Five roles per organisation: owner, admin, manager, agent and viewer.
  • Agents see leads assigned to them, created by them, or shared with them.
  • Teams can be private or have team visibility, where members see each other’s leads. Team managers always see and can reassign their team’s leads.
  • Reporting lines: a manager sees the leads of the people who report to them.
  • Share one lead with a user or a team, as viewer or editor. A viewer stays read-only even when shared as editor.
  • Admins can ask “why can this person see this lead?” and get the exact rule that grants it.
  • The same rules filter every list, search and export, so nothing leaks through a side door.

09

Import and export

Bring your existing leads in on day one, and take them out whenever you like.

  • CSV import with column mapping, a preview of the first 20 rows, and default owner, team and stage.
  • Duplicates: skip them, update the existing lead, or create anyway.
  • Files up to 1,000,000 rows, processed in the background with progress shown.
  • Export the current filtered view to CSV. Export is a permission you grant, not a default.

10

Dashboard and reports

Managers see their teams. Agents see themselves.

  • Today at a glance: new leads, follow-ups due, overdue now, calls made, connect rate, won this month.
  • Pipeline funnel by stage, calls by disposition over 7 or 30 days, and activity over time.
  • An agent leaderboard with calls, connects, wins and overdue follow-ups.

Try it on your own leads.

Free for up to 3 users. Import a CSV and book your first follow-up in a couple of minutes.