Email us
For support, feature requests, and business inquiries, email:
Please don’t email PHI/PII
To keep things safe and compliant, do not send protected health information (PHI), personal data, or full EDI files containing sensitive data via email.
- Prefer redacted samples (remove names, member IDs, addresses, etc.).
- If you need help, share the specific segment(s) and a short description of the issue.
What to include in a support email
- Transaction type: 835, 837P/I/D, 834, 270, 271, 277CA, 999, 850 Purchase Order, 855 Purchase Order Acknowledgment, 810 Invoice, 856 Ship Notice / Manifest, 940 Warehouse Shipping Order, 945 Warehouse Shipping Advice, 997 Functional Acknowledgment, 846 Inventory Inquiry/Advice, and 852 Product Activity Data, or “not sure.”
- What you expected vs what happened.
- Browser + version (Chrome/Edge/Firefox/Safari).
- Export format: CSV, Excel, JSON, or XML.
- Any console error: press F12 → Console (copy/paste the error text).
Quick answers
Do you upload or store my files?
Supported EDI contents are processed locally in your browser, reducing the need to transmit them to the application server.
Can you sign a BAA?
Browser-local processing reduces the need to transmit PHI, but BAA requirements depend on the actual service relationship, data flow, contracts, and applicable obligations. If you have compliance questions, email us and we’ll discuss your use case.
Can you help troubleshoot a specific payer format?
Yes — please send a redacted snippet and the segment(s) you’re seeing issues with.
Where can I learn how it works?
See How it works and Safety & privacy.