SaaS Ranking
Menu

CallN

calln.com · Contact centre · checked 2026-09-14

22/100FBand F

Rank 19 of 46 in Contact centre, where the median is 17.

We measured 12 of 12 criteria for CallN on 2026-09-14. We found 3 with a source and did not find 9 at the addresses we checked. That is a transparency score of 22 out of 100, band F.

Overview

0 days since the newest finding, 0 since the oldest. 12 of 12 criteria measured in the last 30 days.

Evidence freshness is a statement about our measurement and is kept apart from the transparency score, which is frozen at v1. How good our own measurement is.

Transparency labelsaas-ranking.com

CallN

calln.com · Contact centre

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
F 22of 100 Rank 19 of 46

Published commitments3 of 9 found

Measured behaviour0 of 3 found

Checked 2026-09-14. Every line links the page we found it on. A cross means we found nothing at the addresses we checked, not that the vendor has no such document. A transparency score, not a product rating.

The evidence pack carries every criterion with its source, the addresses we checked, the date and the data snapshot id – the four things a procurement file needs and a screenshot loses. We do not issue badges: a badge is the first step towards a paid placement, and there is none here.

The label is the whole measurement in one object: every criterion with its weight, the band, and the date. Public transparency score, not a product or security rating.

Every line in it links the page we found the result on, or lists the addresses we checked. A cross means we found nothing there, not that CallN has no such document.

Where CallN sits in Contact centre

  1. A0 0%
  2. B0 0%
  3. C3 7%
  4. D6 13%
  5. E7 15%
  6. F30 65%
46 vendors with a score; 1 more without a score because we could measure too little. Bands have fixed thresholds, see how the score works.

The band of CallN is marked. Vendors without a score are the ones where we could measure too few criteria to rank them – a gap on our side, counted separately.

What they state

The exact figures and names we read off the pages linked below, with the sentence they stand in. This is what they publish, not what we verified about their systems.

Gaps, heaviest first

✗

Data processing agreement

weight 3 of 3

No data processing agreement found.

Checked 8 addresses on 2026-09-14.

Show the 8 addresses we checked
  1. https://calln.com/legal/dpa – reached, no match (HTTP 404)
  2. https://calln.com/dpa – reached, no match (HTTP 404)
  3. https://calln.com/legal/data-processing-agreement – reached, no match (HTTP 404)
  4. https://calln.com/data-processing-agreement – reached, no match (HTTP 404)
  5. https://calln.com/legal/data-processing-addendum – reached, no match (HTTP 404)
  6. https://calln.com/legal/gdpr – reached, no match (HTTP 404)
  7. https://calln.com/trust/dpa – reached, no match (HTTP 404)
  8. https://calln.com/privacy/dpa – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

Subprocessor list

weight 3 of 3

No subprocessor list found.

Checked 7 addresses on 2026-09-14.

Show the 7 addresses we checked
  1. https://calln.com/legal/subprocessors – reached, no match (HTTP 404)
  2. https://calln.com/subprocessors – reached, no match (HTTP 404)
  3. https://calln.com/sub-processors – reached, no match (HTTP 404)
  4. https://calln.com/legal/sub-processors – reached, no match (HTTP 404)
  5. https://calln.com/trust/subprocessors – reached, no match (HTTP 404)
  6. https://calln.com/privacy/subprocessors – reached, no match (HTTP 404)
  7. https://calln.com/legal/subprocessor-list – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

Status page with history

weight 2 of 3

No public status page found.

Checked 3 addresses on 2026-09-14.

Show the 3 addresses we checked
  1. https://status.calln.com/ – Could not be fetched: fetch failed.
  2. https://calln.com/status – reached, no match (HTTP 200)
  3. https://calln.com.statuspage.io/ – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

✗

Public pricing

weight 2 of 3

No public pricing with figures found.

Checked 5 addresses on 2026-09-14.

Show the 5 addresses we checked
  1. https://calln.com/pricing – reached, no match (HTTP 404)
  2. https://calln.com/pricing/ – reached, no match (HTTP 404)
  3. https://calln.com/plans – reached, no match (HTTP 404)
  4. https://calln.com/en/pricing – reached, no match (HTTP 404)
  5. https://calln.com/pricing-plans – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

HTTPS enforced with HSTS

weight 2 of 3

No enforced HTTPS with HSTS found.

Checked 2 addresses on 2026-09-14.

Show the 2 addresses we checked
  1. http://calln.com/ – redirects to https://calln.com/
  2. https://calln.com/ – no HSTS header

Is this wrong? Send us the URL

✗

No third-party tracking before consent

weight 2 of 3

Third-party requests seen on the first load, before any interaction.

Checked 1 address on 2026-09-14.

Show the 1 address we checked
  1. https://calln.com/ – third-party requests before any interaction: ad.doubleclick.net, assets.zendesk.com, ekr.zdassets.com, encrypted-tbn0.gstatic.com, pi.pardot.com, region1.analytics.google.com, static.zdassets.com, stats.g.doubleclick.net, v2.zopim.com, www.google-analytics.com, www.google.com, www.google.de, www.googletagmanager.com

Is this wrong? Send us the URL

✗

Notice before subprocessors change

weight 2 of 3

No commitment to give notice before subprocessors change found.

Checked 8 addresses on 2026-09-14.

Show the 8 addresses we checked
  1. https://calln.com/legal/subprocessors – reached, no match (HTTP 404)
  2. https://calln.com/subprocessors – reached, no match (HTTP 404)
  3. https://calln.com/sub-processors – reached, no match (HTTP 404)
  4. https://calln.com/legal/dpa – reached, no match (HTTP 404)
  5. https://calln.com/dpa – reached, no match (HTTP 404)
  6. https://calln.com/legal/data-processing-agreement – reached, no match (HTTP 404)
  7. https://calln.com/trust/subprocessors – reached, no match (HTTP 404)
  8. https://calln.com/legal/sub-processors – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

security.txt (RFC 9116)

weight 1 of 3

No security.txt found.

Checked 1 address on 2026-09-14.

Show the 1 address we checked
  1. https://calln.com/.well-known/security.txt – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

Named privacy contact

weight 1 of 3

No named privacy contact found.

Checked 7 addresses on 2026-09-14.

Show the 7 addresses we checked
  1. https://calln.com/legal/privacy – reached, no match (HTTP 200)
  2. https://calln.com/privacy – reached, no match (HTTP 200)
  3. https://calln.com/privacy-policy – reached, no match (HTTP 200)
  4. https://calln.com/legal/privacy-policy – reached, no match (HTTP 200)
  5. https://calln.com/legal/privacy-notice – reached, no match (HTTP 404)
  6. https://calln.com/trust/privacy – reached, no match (HTTP 200)
  7. https://calln.com/datenschutz – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Evidence

The full source lists sit behind these two groups, so that the answer above stays readable.

Published, with a source 3
✓

Data location stated

weight 3 of 3

The hosting location is stated on a public page.

  • Locations named next to the hosting wording Australia, United States.
    Show the 2 exact wordings

    We may use data hosting and other service providers in Australia, the United States or other countries.

    Read at https://calln.com/privacy-policy/

    We may use data hosting and other service providers in Australia, the United States or other countries.

    Read at https://calln.com/privacy-policy/

Source: https://calln.com/privacy-policy/ · checked 2026-09-14

✓

Certifications named

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

  • Named on that page ISO/IEC 27001, PCI DSS.
    Show the 2 exact wordings

    Certifications CallN holds a certification with ISO 27001:2013 as well as being GDPR compliant.

    Read at https://calln.com/security-policy/

    licking the button, you agree to the terms of service and privacy policy WHY SHOULD YOU TALK TO US: PCI DSS Compliant Scalable Architecture Rest Capable Data Encryption End to End SSL User Centric Web...

    Read at https://calln.com/security-policy/

Source: https://calln.com/security-policy/ · checked 2026-09-14

✓

Uptime SLA with a figure

weight 1 of 3

An availability commitment with a figure.

  • Highest uptime figure on that page 100 %.
    Show the exact wording

    Definitions “Monthly Uptime Percentage” is calculated by subtracting from 100% the percentage of minutes during the month in which the Service was in the state of Unavailability

    Read at https://calln.com/sla/

Source: https://calln.com/sla/ · checked 2026-09-14

History

Not enough completed runs yet to draw a line. The next runs fill this in.

Compare

A shortlist holds up to six vendors across categories and lives entirely in the address of its page: share the link, bookmark it, put it in a ticket. Nothing is stored, so we do not know it exists.