Support

Get back to fishing faster.

Start with the Help Center for workflow guides and fast answers, then email support if something still looks wrong.

support@highslack.com Mobile offline logging supported Browser offline queue on new entry
Contact

What to send support

Include the account email, platform, and exact feature or page where the issue happened.
Tell us when it happened and whether the device was online, offline, or reconnecting.
Screenshots, landing numbers, district names, and report years help us reproduce issues much faster.
Before you email:
If sync looks stuck, reconnect the device, reopen the app or the delivery form, and give HighSlack a minute to push queued changes.
How To

Log deliveries offline

Mobile saves entries locally first. On web, open New Tide Entry while online at least once, then that page can keep saving entries in the browser if the connection drops.

  • Mobile: use New Entry, save normally, then reconnect and reopen the app.
  • Web: stay on `/tickets/create`, save offline, then use `Sync Pending` after reconnecting.
How To

Import a past season or processor statement

Go to Deliveries and use Import Season, or use the Audit workflow if you are reconciling processor statements against entries already in HighSlack.

  • Use a real PDF export when possible, not a blurry photo.
  • If a statement layout is unsupported, email support with the processor name and sample file details.
How To

Send or reset a crew onboarding link

Open the crew member record, copy the onboarding link, and send it to the crew member. If the link expires, generate a new one from the crew record and resend it.

Troubleshooting

Common issues

  • App says offline: confirm the device has signal and the user is still signed in to the expected server.
  • Scan failed: try offline scan first; enhanced scan depends on a clearer photo and server-side configuration.
  • Billing looks wrong: open Subscription and compare the active tier, trial status, and manage page details.
  • Push notifications never arrive: enable notifications on the device and reopen the app so token registration can run.
Security

Is my data secure?

HighSlack uses HTTPS in production. Crew SSNs are encrypted at rest when the encryption key is configured. We do not sell operational data to third parties.

FAQ

Frequently Asked Questions

Short answers for the questions users ask most often about setup, sync, scan, crew workflows, billing, and security.

Yes. Mobile supports full offline logging and queued sync. On web, the current browser offline queue lives on /tickets/create after that page has been opened online at least once.

Reconnect the device, reopen the app or keep the delivery form open, and give HighSlack a minute to push queued work. On the web delivery form, you can also click Sync Pending.

Yes. Sign in with the same account on multiple devices. Server-backed data is shared once sync completes. Browser offline queue data is local to that browser until it syncs.

Permit management lives in Settings. If you hit older permit routes, HighSlack redirects them back to the permits section in Settings.

Yes. Use Import Season from Deliveries for bulk import, or the Audit workflow when you want to reconcile processor statements against deliveries already stored in HighSlack.

Retake the photo in better light, fill the frame with the ticket, and try offline scan first. Enhanced scan depends on server-side configuration and can be unavailable even when offline/client-side scan still works.

Each crew member gets a unique onboarding link from their crew record. If the link expires, open that crew member again and reset the token to issue a fresh link.

Yes. The app has crew 1099 and tax-form flows, but the output still depends on complete payer info, crew legal details, and correct year/share data.

Captain is the main self-serve paid tier. Fleet is currently handled as a higher-touch contact/support plan for larger operations.

Send the account email, platform, feature/page, time of failure, online/offline status, screenshot or error text, and any landing number, district, or year tied to the problem.
Terms · Privacy · Help Center · Support