Skip to content

Turn field events into a clear next action.

Review geofence events, send targeted field messages and connect supported events to your own workflow with TeamSpoor.

Start free trial See how it works
  • Entry, exit and breach reports
  • Targeted employee messages
  • Event webhooks
Inside TeamSpoor
TeamSpoor geofence report with entry, exit and breach event views
TeamSpoor screen · sample dataOpen full size
  1. Recorded event
  2. Review
  3. Response
  1. 1Find the event
  2. 2Read the context
  3. 3Choose the response
  4. 4Check the result

Give every event a useful response.

An alert becomes useful when someone understands the event and owns the response. A boundary crossing may need a location check; a schedule change may need a message; a customer event may need to reach another system.

TeamSpoor provides separate tools for these jobs: geofence reporting, a message composer with history, and webhooks for supported field events. Choose the route that fits the operational question, then check the recorded result before repeating the action.

Product walkthrough

Review, communicate or connect the event.

Understand the boundary event before acting.

Filter the period and team, then choose Entry / exit visits or Breach events. Read the fence, recorded timestamps and movement classification with the available location context.

  1. Choose the view

    Use entry/exit for arrival and departure records, or breaches for individual boundary events.

  2. Find the fence or employee

    Use More filters to narrow the investigation.

  3. Read missing values carefully

    A blank exit means no departure was recorded; investigate with the location evidence.

Read the step-by-step guide

Reports → Geofence report

Inside TeamSpoor
TeamSpoor geofence reporting filters and recorded event views
TeamSpoor screen · sample dataOpen full size
Why it matters

The reviewer can identify the recorded event and ask a precise follow-up question.

Keep the instruction specific to the work.

Choose an active permitted executive with a registered device. Enter the instruction, review the recipient and send. Use Message history to find the recorded send attempt.

  1. Name the action

    Include the customer or visit context and the clarification you need.

  2. Review the recipient

    Make sure the instruction reaches the intended executive.

  3. Check the history

    Inspect the recorded message before retrying; confirm receipt directly when the next action is urgent.

Read the step-by-step guide

Messages → Compose a message

Inside TeamSpoor
TeamSpoor message composer and filtered send history
TeamSpoor screen · sample dataOpen full size
Why it matters

A targeted instruction is easier to follow than an ambiguous team-wide update.

Start a workflow in a system you control.

Choose Visits, Attendance or Geofence, configure an endpoint and parameters, then enable after review. Your receiving system can use the event values in its own tested response workflow.

  1. Choose the event

    Select the trigger matching the receiving process.

  2. Map the values

    Use the supported event tags, such as fence name and movement status for geofence events.

  3. Inspect the receiver

    Confirm that a sample matching event produces the intended result in your system.

Read the step-by-step guide

Settings → Webhooks

Inside TeamSpoor
TeamSpoor webhooks configuration and event selection
TeamSpoor screen · sample dataOpen full size
Why it matters

Supported field events can feed an organization-owned response process.

Example workflow

Investigate a missing departure record.

A supervisor reviewing a site visit sees an entry timestamp but no exit in the geofence report.

Illustrative scenario · not a customer result

  1. Review

    Find the fence and employee

    Set the period and employee scope. Read the entry/exit record and confirm which fence it refers to.

  2. Investigate

    Check the supporting location context

    Inspect available location records and the related visit. A blank exit is a missing recorded departure, so avoid inferring the employee’s current position from it.

  3. Respond

    Ask for the specific clarification

    Contact the executive with the site and time in question. Review the message history before sending a duplicate instruction.

What changes

The supervisor resolves the operational question using the event and its supporting context.

Choose the response tool for the job.

Reporting, employee communication and system delivery are distinct workflows.

Swipe across the table to compare all columns.

You need to…UseConfirm afterwards
Review a recorded boundary crossingGeofence reportFence, time, movement and available location evidence.
Give an executive a specific instructionMessagesCorrect recipient and recorded send attempt; direct receipt if needed.
Pass a field event to your own systemWebhookActive configuration and the receiver’s processed result.
Check whether a visit assignment reached the appBeat Plan reportReceived by app, separately from assignment and completion.

Put it to work in your team.

Use the same connected process in the customer interactions your team handles every day.

01

Site movement review

Use recorded geofence entry, exit or breach events to identify a site movement question. Inspect the employee and period, then compare the available visit or attendance record before deciding the next action.

02

Dispatch communication

Send a focused instruction to an executive within scope and review the attempt in message history. Confirm receipt directly when the instruction is time-sensitive or needs a response.

03

Internal event handoff

Use a supported webhook to pass selected field-event values to an organization-controlled endpoint. Test the receiving process and assign ownership for investigating missing or unexpected results.

Make it practical

Try it with one real field workflow.

Choose the event and response that matter most to your team. Identify who reviews it, how they contact the employee and what confirms the action is complete.

Message history and a webhook setting do not by themselves confirm receipt or downstream processing. Include those confirmation steps in your pilot.

Your evaluation checklist

Questions, answered

The details that help you decide.

Need to walk through your own process?

Talk to the TeamSpoor team
Which field events can trigger webhooks?

The documented webhook events are Visits, Attendance and Geofence. Available tags depend on the selected event. Management requires the webhook feature and permission; executives cannot open the webhook management page.

Does message history confirm delivery?

A history row records a send attempt. It does not establish that the executive received or read the message. Confirm receipt directly when it matters and inspect history before retrying an uncertain send.

Can I review geofence entry and exit separately from breaches?

Yes. The Geofence report offers Entry / exit visits and Breach events as different views. Choose the relevant view and scope, then inspect the recorded times and details in context.

Do new webhooks send events immediately?

New webhooks start inactive. Review the endpoint and parameters, then enable the connection to begin delivery for future matching events. Check the receiving system before relying on downstream processing.

Explore all TeamSpoor features

Field reporting

Find customer visits and inspect the information submitted from the field.

See how it fits your field team.

Bring one real workflow to a TeamSpoor trial or demo.

Start free trial Request a demo