Transfer a Request Between Organizations

Some geographies overlap, and requests that should be routed to one organization may be submitted to another organization. The Post to Neighbors transfer workflow documented below is being retired. Starting on or after August 15, 2026, customers should not rely on continued availability of this workflow.

During the transition, if the workflow remains available in your environment, these instructions may still apply. Once the workflow is retired, organizations should direct residents to resubmit requests through the appropriate organization’s portal.

Important Note:

Post to Neighbors is being retired and will no longer be preserved as a request-transfer path between SeeClickFix organizations. Starting on or after August 15, 2026, customers should not rely on continued availability of this workflow.

If a request should be handled by another organization, direct the resident to submit the request through that organization’s portal.

If your organization operates near or overlaps another SeeClickFix jurisdiction, consider enabling Allow reporting to all SeeClickFix 311 CRM organizations in Customize Portal Settings, where appropriate.

Instructions

1. Sign in to your site

2. If the issue was reported to a service category in Organization A, they will need to recategorize the request to the "Post to neighbors" category:

   1. Navigate to the Requests tab:

   2. Check the request:

   3. Click Recategorize:

   4. From the drop-down menu select Post to Neighbors:

   5. Click Update:

3. This will cause the request to become uncategorized, so it will be available for Organization B to access and recategorize:

   1. On the Requests tab, select Post to Neighbors under Categories on the filter menu:

   2. Check the request and click Recategorize:

   3. From the drop-down menu, select the appropriate category:

   4. Click Update: