B2B messaging workflows

Identity checks with a paper-trail point of view.

Verify Current supports business inquiry intake for SMS-based identity verification, document delivery, e-signature coordination, and follow-up workflow review. The current site captures inquiries privately; it does not send SMS or email.

For teams B2B intake, verification, and document follow-up discussions.

For clarity Consent choices are separated from required inquiry fields.

Operator Verify Current is operated by Apex Coverage Group LLC.

A quieter interface for high-friction moments.

This site keeps the form behavior explicit: inquiries are sent to a same-origin API for private storage and operator review, with no external trackers or third-party scripts.

01

SMS identity verification planning

A business can ask about inviting a recipient to confirm identity over an SMS workflow before document delivery or follow-up. The current website collects the inquiry only; SMS delivery is not active yet.

02

Document delivery and e-signature coordination

Inquiry details can describe document packets, signer routing, and handoff needs so the operator can assess a future workflow before any live service is enabled.

03

Follow-up workflow review

Follow-up reminders are framed as prospective workflow communications only. Any live messaging program would need configured templates, support routes, consent handling, and opt-out operations before activation.

04

Consent shown as its own decision

The inquiry form below separates business details from optional future SMS account-notification consent and optional email marketing consent. Neither choice is preselected, and checking either box records a preference only; it does not activate sending or subscription.

A refined verification surface should make the next step legible before it asks anyone to move.

Current intake, future workflow.

This sequence separates what the site does today from messaging, document, and support workflows that would require later activation.

Business intake

A team submits contact and workflow details through the same-site inquiry form. Submissions are stored privately for operator review.

Email validation

The backend checks basic email syntax and DNS/MX where available. It cannot prove that the submitter owns or can receive mail at that address.

Consent record

Optional SMS and email marketing checkbox choices are stored as consent preferences only. There is no automatic subscription or outbound messaging.

Future activation

Live SMS, document, e-signature, follow-up, and support processes are not active from this site and would require configured policies, vendors, support procedures, and operator activation.

Live inquiry

Inquiry capture with consent separated.

Submitting this form sends the data you provide to the same-origin /api/inquiries endpoint. The worker stores inquiries in a private database and checks email syntax plus DNS/MX where available; it does not verify mailbox ownership and does not send email or SMS.

  • SMS account-notification consent is optional, unchecked, and not active sending.
  • Email marketing consent is optional, unchecked, and not an automatic subscription.
  • Privacy and terms are linked on the same site for review.

Business inquiry

Required fields are name and work email. Support mailbox support@verifycurrent.com is not active yet, so this form is the active intake path.