Overview
Provider Connection Requests (sometimes called "sync requests" in support contexts) are how grease providers (haulers) working in SwiftWorks formally link to your FOG program. When a provider starts servicing a new customer, they submit a connection request from SwiftWorks. Until you approve it, the provider cannot submit pump outs for that establishment.
Note on terminology: "Provider" is the FOG term for a grease hauler. SwiftWorks calls them haulers; FOG calls them providers. They're the same companies. The rest of this article uses "provider" throughout.
This article covers the full flow -- where requests come from, what statuses they pass through, and how to resolve them.
Before you start
Your FOG program needs the Provider Connection Requests feature enabled. If you don't see the Connection Requests tab on the Providers page, contact SwiftComply support to turn it on.
When you review each request, you'll be matching it to records in your FOG program -- a provider in your Providers list, and an establishment in your Establishments list. Knowing the provider's name and the establishment's address ahead of time speeds up the review.
If a provider says they can't find your organization in the SwiftWorks dropdown, contact SwiftComply support.
How the connection flow works
A provider adds a new customer (food service establishment) in SwiftWorks.
SwiftWorks sends a Connection Request to your FOG program with the establishment's name and address, plus the provider's information.
The request appears in your Connection Requests list with the status Pending.
You review the request, match it to an existing provider and establishment (or create the establishment from the review screen if it doesn't exist yet), and either approve or reject.
Once approved, the provider can submit pump outs for that establishment through SwiftWorks.
Connection Request statuses
Pending -- the default when a request first arrives. Only pending requests can be approved or rejected.
Approved -- you confirmed the connection. The provider can now submit pump outs for the matched establishment.
Rejected -- you declined the connection. The provider cannot submit pump outs through this request.
Approved and rejected requests are read-only. To reverse a decision, contact SwiftComply support.
Finding pending requests
Click Providers in the left sidebar.
At the top of the Providers page, click the Connection Requests tab.
To focus on what needs your attention, filter Status to Pending.
The list also lets you filter by provider name, establishment name, and the request's created-at date range.
Reviewing a request
Open a pending request to see everything the provider submitted. The review screen has two sections:
Requested Provider Data -- the provider's info as it was submitted from SwiftWorks.
Requested Establishment Data -- the establishment's info (business name, address) the provider is asking to connect to.
Use these two sections to confirm the data lines up with what's in your FOG program before you approve.
Approving a request
Open the pending request from the Connection Requests list.
Review the Requested Provider Data section.
In the provider matching field, select the existing provider that matches. If no provider in your FOG program matches, create one first or reject the request.
Review the Requested Establishment Data section.
In the establishment matching field, select the existing establishment. If the establishment isn't in your FOG program yet, you can create it directly from the review screen as part of approving -- you don't have to leave to the Establishments page first.
Click Approve.
The status flips to Approved, the provider is notified, and pump outs for that establishment can start flowing into FOG. The request also records who processed it and when.
Rejecting a request
Reject when the provider or establishment info is wrong, the provider isn't authorized to service the location, or the request duplicates an existing connection.
Open the pending request.
Click Reject.
The status flips to Rejected, the provider is notified, and they cannot submit pump outs through this request. They can submit a new request later if their info changes.
Common scenarios
The provider doesn't exist in my FOG program yet
Create the provider in FOG first (Providers → Add provider), then return to the request and match it. Alternatively, reject the request and ask the provider to verify their info in SwiftWorks before resubmitting.
The establishment doesn't exist in my FOG program yet
You don't have to leave the request to handle this. On the review screen, in the establishment matching section, create the establishment from the request itself. The new establishment is saved and the connection is made when you approve.
The provider's info looks wrong
Don't approve. Reject the request and reach out to the provider so they can correct their data in SwiftWorks before resubmitting.
I approved the wrong connection
Approved and rejected requests are read-only. Contact SwiftComply support to reverse the decision.
FAQ
Q: How long should I wait before resolving a request?
A: Resolve as soon as possible. Providers can't submit pump outs for the new establishment until you approve, so any delay holds up records reaching your FOG program.
Q: A provider says my organization is missing from their SwiftWorks dropdown. What do I do?
A: Contact SwiftComply support. The Provider Connection Requests feature has to be enabled for your FOG program, and only SwiftComply can turn it on.
Q: Can a provider submit a pump out before I approve the connection?
A: No. Pump outs from that provider for that establishment are only accepted after the request is approved.
Q: Can I edit a request after approving or rejecting it?
A: No. Approved and rejected requests are read-only. To reverse a decision, contact SwiftComply support.
Q: Can I filter the Connection Requests list?
A: Yes -- by status, provider name, establishment name, and the request's created-at date range.
Q: Will the provider see my decision?
A: Yes. The provider's SwiftWorks account shows whether their request was approved or rejected.
Q: What does the request ID do?
A: It's a unique identifier FOG assigns when the provider submits. Use it when working with SwiftComply support to reference a specific request.