Retained evidence
Capture and organize records that support internal follow-up, customer service, and audit preparation.
Document & Fax Records
Document and fax-record operations around the systems you already use.
Med Pulse supports the operational layer around fax-dependent workflows: retained records, delivery confirmations, archive retrieval, and review support. Customers keep their underlying fax transmission systems; Med Pulse organizes the evidence, service context, and support workflow around them.
Service boundary: Med Pulse does not provide the underlying fax sending or receiving capability. This service line supports the archive, evidence, notification, and review work around existing fax-dependent workflows.
Document & Fax RecordsService line
ArchiveSignalConfirmWorkflowReviewReview
Product-specific support intake and account contextStandalone service options with monthly pricingDocumented follow-up through online support workflows
What it covers
Document & Fax Records is built around practical operating workflows.
Delivery context
Store delivery confirmations and exception details so teams can understand what happened after the fact.
Review workflows
Use ticketed support and recurring review to investigate unusual activity or operational questions.
Standalone services
Available products in Document & Fax Records.
These services can be scoped individually or combined into one of the Med Pulse customer-size packages.
Fax Archive Retention
Secure cloud archive support for inbound and outbound fax-related records with search and retrieval workflows.
Fax Delivery Confirmation
Automatic capture and storage of delivery confirmation receipts for outbound fax-related activity.
Fax Security Log Review
Quarterly review of fax-related transmission logs for unusual activity, service questions, and follow-up recommendations.
Fax Number Spoofing Monitoring
Inbound traffic review to help identify spoofing patterns, suspicious sender behavior, and escalation needs.
Customer value
Why teams add this line to the Med Pulse service model.
Each product line is designed to create clearer operating context, cleaner support handoffs, and better documentation around the communication workflows customers already rely on.
Less inbox archaeologyTeams can request retained context instead of searching across scattered emails and local folders.
Clearer follow-upDelivery confirmation and archive details help support teams understand customer questions faster.
Better compliance preparationRecords are structured around retrieval, review, and support documentation needs.
Portal workflow
Service context, requests, and documentation stay connected.
Customers can use the portal experience to route support requests, review archive context, coordinate API-enabled events, and keep operational records close to the work.
API context
Manage notification, evidence, and archive permissions from one workspace.
Operations teams can scope API access by environment, permitted actions, and technical owner before connecting ancillary service events to internal systems.
Service API
Production eventsActive
Allowed IPs3 ranges
Webhook endpointVerified
NotifyEvidenceArchive
Document archiving
Retrieve transmission records and evidence packages without chasing inboxes.
The archive workflow gives authorized users structured search, retained transmission metadata, and documentation packages for audits or internal review.
Archive retrieval
Date rangeFacilityStatus
Transmission recordDeliveredCompliance bundleReadyRouting recordReview
Next step
Scope Document & Fax Records for your organization.
Tell us about your locations, systems, support expectations, compliance priorities, and the communication workflows you need to strengthen.
