TickFlowTickFlowField
PricingFAQ
Sign In
Book a demo
Skip to content
  • Overview
  • How it works
  • Security
  • Platforms
  • Integrations
  • Solutions
  • Developers
  • Trust
  • Pricing

Integrations

Field fits the tools you already run.

Your service desk keeps being the place your team works. Field sends it the diagnosis, hears back when someone acts, and connects to the rest of your stack through webhooks, API keys, single sign-on and SDKs.

Field
  • Your service deskincidents · tickets
  • Your own toolswebhooks · API keys
  • Your sign-inOIDC · SAML
  • Your appsAndroid · React Native · iOS

Service desks

A report becomes an incident. Replies come home.

Choose which reports to send and where. Each one opens in your desk with what an agent needs to act, and a link to everything else. Your agents keep working in their own queue; Field keeps its timeline in step.

  • works withServiceNowRolling out
  • works withZendeskRolling out
  • andMore on requestOn request
FieldFR-1001
Card reader not respondingDowntown T-06 · lane 2Likely cause reader session not re-openednewin progress · syncedfrom your desk“Approved for tonight’s window.”
report · summary · linkstatus · replies
Your service deskIncident #48213
Short description
Card reader not responding · Downtown T-06
Assignment
Merchant support
Evidence summary
2 screenshots · 30 min of logs · reader error after a USB reset
Field report
Open in TickFlow Field ↗
Dana K. · agentApproved for tonight’s window.
NewIn progress
Illustrative. Your desk’s own fields and workflow decide what it looks like.
  • Rolling out

    ServiceNow

    A Field report opens an incident in your instance, assigned the way your team already assigns them.

  • Rolling out

    Zendesk

    A Field report opens a ticket for your support team, in the queue they already work from.

  • On request

    More on request

    Built to add service desks. Tell us which one you run and we will tell you where it sits on the roadmap.

What syncs

Enough to act on. Nothing your policy keeps in.

The summary, at the level your service-desk owner will ask about. Field maps it onto your desk’s own fields when we set it up with you.

→From Field to your desk

  • A new incident or ticket for each report you choose to send
  • A short evidence summary: device, app version, what the person saw
  • The likely cause and how confident Field is
  • A link back to the full report in Field
  • Progress: approval waiting, fix running, fix verified

←From your desk back to Field

  • Status changes made by your agents
  • Replies and internal notes, on the Field report's timeline
  • Resolution, so both sides close together

Never sent

  • Card data: it never leaves the terminal in the first place
  • Raw logs and screenshots: they stay in Field, one click away behind your sign-in
  • Anything your policy keeps internal

The rest of your stack

Your tools, your sign-in, your apps.

Everything a customer connects is created, scoped and revoked by your own administrators in your portal, and every change is in your audit log.

  • Rolling out

    Webhooks

    Tell your own tools the moments that matter: a report filed, a diagnosis ready, an approval waiting, a fix verified. Deliveries are signed so you can check they came from us.

  • Rolling out

    API keys

    Create keys in your portal, give each one only what its tool needs, and revoke it in one click. Every call is in your audit log.

  • Available

    Single sign-on

    Your identity provider over OIDC or SAML, enforceable for your whole organisation, for domains you have proved you own.

  • Rolling out

    SDKs for your own apps

    Android, React Native and iOS: your app's own errors and context on every report, from inside the app.

    SDKs on the platforms page

Building against the device protocol itself? The developers page has the signing rules and a demo you can try to break.

Tell us which service desk you run.

We will show you a report arriving in a desk like yours, an agent replying, and the Field timeline catching up, in a 30-minute demo.

Book a demoEstimate your savings

Or write to hello@tickflow.co

Report a problem.
TickFlow Field

On-demand diagnosis and remote repair for payment terminals and field devices. Part of the TickFlow family, built by Orthoplex Solutions in Canada.

hello@tickflow.co

Product

  • How it works
  • Security & PCI
  • Platforms
  • Integrations
  • Product tour
  • Playbook catalog
  • Compare
  • Pricing

Solutions

  • Savings calculator
  • Banks & acquirers
  • ISOs & resellers
  • Retail & QSR
  • Kiosk operators

Developers

  • Developers
  • Trust centre
  • Changelog

Field

  • Book a demo
  • Open Field
  • Privacy policy
  • Terms of service
  • Report a vulnerability
© 2026 Orthoplex Solutions. TickFlow and TickFlow Field are products of Orthoplex Solutions.Pilot targets and figures marked illustrative are not results.ServiceNow, Zendesk and ClickUp are trademarks of their respective owners (ClickUp™ of Mango Technologies, Inc.), named to show compatibility; no partnership is implied, and TickFlow is not affiliated with, endorsed by or sponsored by them.