TickFlowTickFlowSDK
PricingFAQ
Sign In
Talk to us
Skip to content
  • Overview
  • How it works
  • Privacy & security
  • Developers
  • Pricing

How it works

One shake. One ticket. No “can you send a screenshot?”.

Step through one report from a beta build: what happens on the phone, what arrives in TickFlow, and who is in control at each point.

14:32
‹ CartCheckout
  • Trail runnerSize 9 · Blue$129.00
  • Running socks3 pack$18.00
Saved card ···· 4242
Total$147.00
Payment failed. Please try again.
Pay $147.00
Report a problemSends a ticket to the team behind this app
ScreenshotInclude screenshot
Title *
What went wrong?Checkout fails after Pay
Attach diagnostics (logs.zip)212 log lines · 1 error · 34 network calls · iPhone 16, iOS 19.1
[LOG] POST /checkout Authorization: Bearer [redacted][WARN] Payment request failed, status 502[ERROR] TypeError: Cannot read property 'id' of undefined
Send report
Thanks, your report was sentQuote this reference if you follow up:TF-8F42-QKDone

Step through it

One report, start to finish.

Use the tabs or the arrow keys. Each step shows the phone, TickFlow and who is in control side by side.

On the phone
The SDK keeps the recent console lines, JavaScript errors, network calls and your breadcrumbs, from the moment the app starts. Secrets and e-mail addresses are replaced as each value is captured.
In TickFlow
Nothing. Nothing leaves the phone until someone sends a report.
Who is in control
You. One switch decides which builds include it at all: internal, QA or beta. Switched off, it does nothing.
console · captured on the phone3 secrets → tokens
14:31:52 [LOG] Navigated to Checkout
14:31:53 [LOG] GET https://api.shop.example/cart?session=8f2a91c4e7d0[redacted]
14:31:58 [LOG] Receipt e-mail set to dana.k@example.com[email]
14:32:01 [LOG] POST /checkout  Authorization: Bearer 0f9e8d7c6b5a4f3e[redacted]
14:32:02 [WARN] Payment request failed, status 502
14:32:02 [ERROR] TypeError: Cannot read property 'id' of undefined
redacted as it is capturedkept on the phoneleaves only when someone sends a report
1 / 5

Before the first report

Three steps, one of them in TickFlow.

  1. 01

    Allow the app

    In TickFlow, an admin opens Collect Feedback for the client account, adds the app’s bundle id or package name and creates an embed key.

  2. 02

    Add it to the app

    Your developer installs the package and adds a few lines around the app. Your TickFlow contact sends the setup guide.

  3. 03

    Shake to report

    Testers shake the phone, check what will be sent, add a few words and send. The ticket arrives with the evidence attached.

The same embed key can serve a client’s website feedback widget and their app.

In your app

A few lines in your app. Nothing else changes.

Only in the builds you choose

One switch keeps it to internal, QA or beta builds. Switched off, it does nothing at all.

Shake, or a menu item

Shake detection is on by default. Turn it off and open the same card from a Report a problem item in your own menu.

Your logging keeps working

Your console output and crash reporting behave exactly as before. Add breadcrumbs and context where they help.

Detailed technical briefing available on request

The how behind this page — how the SDK hooks into your app, the integration guide with code, and the redaction rules — is in our technical briefing for customers, security teams and assessors. Ask us for access, then sign in.

Sign in to the briefing →

See a report land in your own TickFlow.

TickFlow SDK comes with TickFlow Web plans from $200/month. Talk to us, or upgrade your plan, and your testers can shake to report.

Talk to usSee SDK pricing

Or write to hello@tickflow.co

Shake to report.
TickFlow SDK

In-app bug reporting and testing for mobile apps. Reports land as TickFlow Web tickets, built by Orthoplex Solutions in Canada.

hello@tickflow.co

TickFlow SDK

  • Overview
  • How it works
  • Privacy & security
  • Developers
  • Pricing

TickFlow

  • TickFlow Web
  • TickFlow Field
  • All pricing
  • FAQ
  • Privacy policy
  • Terms of service

Get started

  • Talk to us
  • SDK pricing
  • Technical briefing
© 2026 Orthoplex Solutions. TickFlow and TickFlow SDK are products of Orthoplex Solutions.The app, device and report shown on these pages are illustrative.TickFlow is an independent product and is not affiliated with, endorsed by, or sponsored by ClickUp. ClickUp™ is a trademark of Mango Technologies, Inc.