Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.sensorup.com/llms.txt

Use this file to discover all available pages before exploring further.

Follow-up requests getting started illustration

​
Welcome!

Follow-up requests transform how you handle emission events by enabling you to initiate standardized investigation, triage, and resolution workflows directly from the platform. Instead of juggling multiple systems and manual processes, you can streamline everything from quick operational comments to complex field inspections with just a few clicks.
Time Required: 10 minutes to complete your first follow-up requestWhat You’ll Learn:
  • How to create your first follow-up request from an emission event
  • The different types of follow-up actions available
  • Best practices for streamlining your investigation workflows
Before You Start:
  • Your organization must have follow-up requests enabled for your account
  • You’ll need appropriate permissions to create work items and requests
  • Some request types may require additional configuration by your administrator

​
Your First Steps

1

Navigate to an Emission Event

Start by opening any emission event from your dashboard, timeline, or asset view. Look for events that need investigation or follow-up action.The follow-up request options will appear as action buttons in the event details panel.
2

Choose Your Follow-up Action

Select the most appropriate follow-up request type for your situation:For Quick Triage:
  • Ops Comment: Get operator input on whether this is a known operational activity
  • Email Notification: Alert supervisors about high-priority events
For Detailed Investigation:
  • Field Inspection Request: Dispatch technicians for on-ground verification
  • Data Collection Form: Capture structured information from operators
Selecting a follow-up action from an emission event
3

Complete the Request Details

Fill out the request form with relevant information:
  • Request description: Explain what you need and why
  • Priority level: Set urgency based on the event’s significance
  • Recipients: Add email addresses for people who should be notified
  • Attachments: Include any supporting documents if needed
The form will guide you through the specific information needed for your chosen request type.
4

Submit and Track

Once submitted, your follow-up request creates a trackable work item that:
  • Appears in your team’s workflow management system
  • Sends notifications to the people you specified
  • Links back to the original emission event for full context
  • Can be monitored for completion and results
You Did It!✅ Created your first standardized follow-up request✅ Initiated a trackable workflow from an emission event✅ Set up automatic notifications for your team

​
Viewing and Managing Issues in the Emission Event Blade

After you create follow-up requests, the resulting Issues are accessible directly within the emission event detail view. You no longer need to navigate to the Issues page to check on work status or manage tasks.
Emission event blade with embedded Issue details panel showing an OGI Inspection task
When you open an emission event, a secondary blade (panel) displays all related Issues inline. This embedded Issues blade provides full parity with the Issues page, so you can stay in the emissions context while managing your work.
From the embedded Issues blade, you can:
  • View tasks and their current status: See the progress of each follow-up request at a glance
  • Review results: Check inspection findings, operator comments, and data submissions without leaving the emission event
  • Add comments: Collaborate with your team by posting updates or asking questions directly on an Issue
  • Track status updates: Monitor changes to Issue status as work moves through your organization’s workflow
Use the embedded Issues blade to quickly confirm whether a follow-up request has been addressed before creating additional requests for the same event.

​
Types of Follow-up Requests

Understanding the different request types helps you choose the right workflow for each situation:

Ops Comment

Best For: Quick triage to determine if an event is operational or a potential leakWhat It Does: Routes a question to operators who can provide context about planned activities or equipment statusTimeline: Usually resolved within hours

Field Inspection

Best For: Events that need visual confirmation or on-ground investigationWhat It Does: Creates a formal work order for technicians to visit the site and conduct inspectionTimeline: Typically scheduled within 24-48 hours

Data Collection

Best For: Gathering structured information about equipment, repairs, or operational activitiesWhat It Does: Sends custom forms to operators to capture specific details needed for your analysisTimeline: Response time varies based on form complexity

External Integration

Best For: Organizations using external maintenance or field service systemsWhat It Does: Automatically creates work orders in your existing systems without manual data entryTimeline: Immediate integration with external workflows

​
Best Practices

Do This

Action: Use Ops Comments first for quick triageWhy: This helps you avoid dispatching resources to investigate known operational activities, saving time and costs.

Do This

Action: Include specific details in your request descriptionsWhy: Clear context helps responders understand what you need and respond more effectively.

Not That

Action: Don’t create multiple requests for the same event without coordinationWhy: Duplicate requests can lead to confusion and wasted effort from your field teams.

Not That

Action: Don’t skip adding email recipients for urgent requestsWhy: Without notifications, important requests may sit unnoticed in work queues.

​
Advanced Workflows

Once you’re comfortable with basic follow-up requests, explore these advanced capabilities:
Some organizations have follow-up requests that integrate directly with mobile field applications. When you create these requests, technicians receive them on their devices with:
  • GPS navigation to the event location
  • Event context and history
  • Forms for capturing inspection results
  • Photo and document upload capabilities
Your organization can configure custom follow-up request types that match your specific operational procedures. These might include:
  • Specialized inspection protocols
  • Integration with regulatory reporting systems
  • Custom approval workflows
  • Automated escalation procedures
For events that are clearly related (such as multiple detections from the same leak), you can group them together and create a single follow-up request that covers all related observations, avoiding duplicate work.

​
If You Get Stuck

Possible Causes:
  • Follow-up requests aren’t enabled for your organization
  • Your user account doesn’t have the required permissions
  • The specific event type doesn’t support follow-up requests
Solution: Contact your system administrator to check your account settings and permissions.
Possible Causes:
  • Email addresses were entered incorrectly
  • Recipients’ email systems blocked the notification
  • There was a temporary system issue
Solution: Check the request details to verify email addresses, and consider following up directly with recipients.
Solution: Navigate to the work item created by your request. Depending on your system configuration, you may be able to update details or add comments. For urgent changes, contact the assigned recipient directly.

​
What’s Next?

Now that you understand follow-up requests, explore these related features to build more comprehensive workflows:

Event Grouping

Learn how to group related emission observations before creating follow-up requests to avoid duplicate investigations.

Root Cause Analysis

Discover how to use investigation tools and operational context to determine the source of emission events.

​
The Art of the Possible: Custom Workflows

The true power of follow-up requests lies in their configurability. While you’ll only see the request types your organization has enabled, the possibilities are extensive. By working with your Customer Success Manager, you can transform your company’s unique operational processes into powerful, integrated workflows directly within the platform—from simple notifications to deep, bi-directional system integrations. Whether you need to integrate with maintenance systems, dispatch mobile teams, or create custom approval workflows, follow-up requests can be tailored to match your existing processes while eliminating manual data entry and improving response times.