JevShield API documentation

Save business context, a notification destination and a public HTTPS booking page in Dashboard → Routing. Choose email to your verified account, Slack, Discord, Teams Workflows, or a custom webhook for Zapier, Make and other automations.

Different messengers and calendars work together

Your team can use Slack while your visitor uses email and Outlook. Share a web booking page from Calendly, Cal.com, Google appointment schedules or Microsoft Bookings. Connect the calendars that determine your availability inside that service. It handles time zones, conflicts, invitations and changes according to its settings and plan.

For iCloud availability, verify the provider supports a new iCloud connection. Apple Calendar can also display a connected Google or Exchange account. An ICS download is an event snapshot, not a live availability check or a synchronized cancellation workflow.

Connect a team notification

• Slack: create an Incoming Webhook for a channel, select Slack, and paste its URL. Notifications use plain text without automatic mention parsing.
• Discord: create a channel webhook, select Discord, and paste its URL. JevShield requests confirmation and disables automatic user or role mentions.
• Teams: use Workflows with a webhook trigger and an Adaptive Card action. Select Teams Workflows and add a co-owner. Legacy Office 365 Connectors are not the recommended setup.
• Zapier or Make: use a Catch Hook or Custom Webhook, then map contact and intent fields to your CRM or messenger. Telegram requires an authorized bot and chat; WhatsApp requires its own business messaging setup and recipient permission.

Send sample notification tests your selected services without using detection quota. The latest attempt shows HTTP acceptance or failure. This is not a delivery or read receipt. There are no automatic retries; configure downstream deduplication with event_id when using automations.

Custom webhook payload

{
  "event": "lead.high_intent",
  "event_id": "example-event-id",
  "lead_score": 92,
  "lead_intent": "sales_inquiry",
  "is_high_intent": true,
  "recommended_action": "book_meeting",
  "sender_name": "Example visitor",
  "email": "[email protected]",
  "site": "example.com",
  "booking_url": "https://cal.com/your-team/intro",
  "timestamp": "2026-10-05T12:00:00.000Z"
}

Example values are illustrative. The message field is included only when enabled. Use a destination you control and explain AI processing and notification providers in your form privacy notice.

Show booking after confirmed form success

Server integrations receive meeting_url for eligible high-intent results. Render it as an optional HTTPS link on your success screen after your form handler confirms success. Keep the original confirmation visible. Do not redirect on a timer or treat a classifier response as email delivery.

The optional browser helper emits a submission_id with formshield:verified. Pass the matching ID back in formshield:submitted only from your form’s confirmed success callback. The helper then offers a booking link for an eligible result. A block, review, failed submission or stale callback must not open a booking page.

// Add this listener once to the form already used by your integration.
let checkedSubmission;
form.addEventListener('formshield:verified', (event) => {
  checkedSubmission = event.detail.submission_id;
});

// Adapt your EXISTING AJAX submit handler; do not add a second submit listener.
async function yourExistingSubmitHandler(event) {
  event.preventDefault();
  const submission_id = checkedSubmission; // Capture before this request starts.
  checkedSubmission = undefined; // Never carry an old check into a later request.

  // Keep your actual delivery request and its success condition here.
  const result = await sendYourExistingForm(new FormData(form));
  if (result.confirmedSuccess && submission_id) {
    form.dispatchEvent(new CustomEvent('formshield:submitted', {
      detail: { submission_id } // This request's ID, never a later global value.
    }));
  }
}

The WordPress plugin keeps the original form delivery flow and does not automatically display a booking button. Add the booking link in your form’s success action, or use a custom server integration. A Google Meet, Zoom or Teams meeting URL is selected by your booking service; both people join using its supported browser or app.