Skip to content

Connecting Uspacy

Connecting takes two actions in Uspacy: installing the app and activating call processing. Aelo receives no calls until processing is activated.

Step 1: Install the app from the Uspacy Marketplace

Install Aelo from the Uspacy Marketplace. On the first installation Aelo creates an organization named after your portal’s domain, marked “(Uspacy)”, with one project that becomes its default project. The organization starts in Manual mode. Reports are set to go back to Uspacy: as a note on the call and as a comment on the linked record.

Installing does not start taking calls: Aelo subscribes to the portal’s call activity only after activation (step 2).

Installing the app again on a portal Aelo already knows returns it to the organization it belongs to instead of creating a new one.

Step 2: Activate processing in Uspacy

Open the Aelo app’s page in Uspacy. The person who installed the app sees “Review the documents before activation” and two confirmations, both unchecked:

  1. On behalf of the organization, accepting the Terms of Service (including the Uspacy Integration Terms) and the Data Processing Agreement.
  2. That they have read the Uspacy Integration Privacy Notice.

After ticking both, they click Confirm and activate. Aelo records the acceptance, creates or links their Aelo account by the email address of their Uspacy profile — on a new organization they become its owner — and subscribes to the portal’s call activity. The page then says “Connected” and what happens to new calls.

Only the person who installed the app may activate it: anyone else sees “Administrator action required”. The documents are the governing English text; the page says so when your interface language is another one.

Connecting the portal to an existing Aelo organization

If your company already uses Aelo, you can attach the portal to that organization instead of the one the installation created — as long as the app has not been activated yet.

  1. In Uspacy, the person who installed the app opens the app’s page and chooses “I already have an Aelo organization — link this portal to it”. Aelo opens in a new tab.
  2. Signed in to Aelo as the owner or an admin of the organization, on the Connect Uspacy page they tick the same two confirmations and click Connect portal.

The link from Uspacy works once and for 10 minutes; if it has expired, start again from the app’s page. The portal is not attached when the organization has no default project or is already connected to another Uspacy portal, and not when the organization the installation created already has members or records: then contact support.

Once attached, the portal follows the organization’s analysis settings, and processing is active. From then on, processing is paused, withdrawn and turned back on only in Aelo settings by the organization’s owner or an admin; the app’s page in Uspacy says “Confirm in Aelo settings”.

Step 3: Choose when analysis starts

The organization the installation created starts in Manual mode: calls come in and wait with the status Awaiting start, and no minutes are spent until an owner or admin starts them — one at a time, by selection, or the accumulated backlog in runs of up to 200 calls (repeat it while calls remain), with the price shown first. To have every new call analyzed as it arrives, switch the organization to Automatic under Settings → Organization → Analysis mode, or click Turn on automatic analysis on the Records banner. Calls that arrived before the switch keep waiting until you start them. See Automatic and Manual Analysis.

A portal attached to an existing organization keeps that organization’s mode.

In Automatic mode the project’s own settings still apply: with Automatic analysis after transcription off, a call is transcribed and waits for its analysis to be started; in Transcript only mode it is transcribed without analysis. The app’s page in Uspacy shows which of these applies to new calls.

Step 4: Check what goes back to Uspacy

Under Analysis Setup → CRM Updates the Owner and the Admin choose what Aelo writes into Uspacy: Report as a note (on the call), Report as a comment (on the linked deal, lead, contact or company) and, on Pro and higher plans and in the Pro trial, Deal state comment. The step exists for every Uspacy organization, on any plan. See What goes back into Uspacy.

Pausing, withdrawing and disconnecting

The organization’s owner or an admin manages processing under Settings → Compliance → Consent Management, on the Uspacy organization processing card:

  • Pause stops taking new calls. Calls already received that wait for a start cannot be started while processing is paused, and no minutes are spent on them; re-analysis of such a call is refused too.
  • Withdraw instruction stops processing in the same way, with a confirmation. Turning it back on takes a new instruction from an authorized representative.
  • Reauthorize processing turns processing back on: tick the two confirmations for the current documents first. Calls that waited are not started by it — start them as usual.

Either way, Aelo first stops accepting new calls and then removes its subscription to your portal. Records and analyses already made stay in Aelo. The person who installed the app can also turn processing back on from the app’s page in Uspacy — only while they are still the organization’s owner, the portal was not attached to an existing organization and processing has never been turned back on in Aelo settings. After that, it is turned back on in Aelo settings only.

Disconnecting the source under Settings → Data Source → Connection also pauses processing, and the app’s page in Uspacy then says “Application not installed” and suggests reinstalling: a reinstall does not resume paused processing, so give consent in Aelo instead. Reconnect does not bring a Uspacy source back: the card says Processing not authorized and offers Give consent, which opens Consent Management. See Data Sources.

Removing and reinstalling the app

Removing the app from the Uspacy Marketplace stops new call intake and deletes the stored portal credentials; the Data Source card says App removed from the portal. Analyses already made remain until the organization’s retention period ends or deletion is requested. Removing the app does not withdraw processing: install it again and processing resumes as it was, without new confirmations, together with the reports to Uspacy. Processing you paused or withdrew in Aelo settings stays that way after a reinstall.

Troubleshooting

The app’s page says “Administrator action required”

Only the person who installed the app can activate it. Ask them to open the app’s page in Uspacy.

The app’s page says “Confirm in Aelo settings”

Processing of this portal is turned on in Aelo, not in Uspacy: the portal was attached to an existing organization, or processing was already turned back on in Aelo settings once. The owner or an admin of that organization opens Settings → Compliance → Consent Management and clicks Reauthorize processing.

The app’s page says “Activation is incomplete”

The confirmations were saved, but the subscription to the portal’s call activity was not created. If the app was activated from Uspacy, the person who installed it clicks “Retry activation” on the app’s page; otherwise the owner or an admin clicks Reauthorize processing under Settings → Compliance → Consent Management. If it repeats, contact support.

The app’s page says “Reauthorization required”

Uspacy no longer accepts the credentials Aelo stored. Install the app from the Uspacy Marketplace again.

Calls do not appear in Aelo

  • Processing must be active: check the app’s page in Uspacy or the Uspacy organization processing card.
  • The call must have taken place and have a recording; a call made before activation comes in only if someone edits it in Uspacy after activation.
  • The organization needs a default project with calls switched on. See Projects.

Calls are in Aelo, but not analyzed

In Manual mode calls wait with the status Awaiting start until you start them. A call shorter than the project’s Min Call Duration (sec) threshold is transcribed only, and a missed call is not processed.

The report is on the call, but not on the deal

The comment goes only to a record the call is linked to in Uspacy, and only when Report as a comment is on. If your organization delivers results to Bitrix24, Uspacy receives neither notes nor comments, nor the deal state comment.