Assign and share a contact from the IllyVoIP app

The mobile contact editor can show ownership, assigned-agent, company and sharing fields for an editable contact. Use the account owner for these administrative ownership, assignment and sharing changes; an agent’s general edit access does not grant the same authority. Use the account’s returned choices. Responsibility, contact visibility and account-wide Portal permissions are different decisions.

These instructions follow the Android app version 1.0.46, build 272. Available actions depend on your account permissions and current service state. Other installed versions may present different controls.

1. Open the exact contact

1. Find the contact in Contact Center and verify its name and number against the intended record.
2. Open Edit using an account authorized to change it.
3. Review its current owner, assigned agent, company and sharing before selecting replacements.
4. Coordinate with other editors if the contact is being updated elsewhere.

Do not identify a contact solely by a display name shared by several people. If the editor or its metadata cannot load, wait or investigate the error; an unavailable choice list is not proof that the contact has no owner or sharing.

2. Distinguish ownership from assignment

Use Owned by for the offered contact-owner choice and Assigned to for the responsible agent. Select only from the choices returned for your account. An assignment can describe responsibility without granting every permission needed to view or edit the record.

A control appearing in the app does not override server authorization. If a change is rejected, inspect the permission or validation message and refresh the available choices. Do not enter another account’s numeric user ID or try to transfer ownership through an unrelated field.

3. Review company and sharing

1. Choose the appropriate existing company where offered.
2. If creating or naming a new company is part of your authorized change, check for an existing match first.
3. Select the intended sharing recipients in the sharing controls.
4. Review removals as well as additions, especially where another teammate depends on access.

Sharing a contact is not the same as granting account-wide contact, billing or webhook permissions. Conversely, an administrator’s visibility does not prove an ordinary agent can see it. Keep the contact’s actual access rules separate from the employee’s account role.

4. Complete required custom fields

The editor loads the configured custom-field definitions. Fill required values and use the field’s type: a number uses dot-decimal notation, a date uses a valid YYYY-MM-DD calendar date, and a URL needs an HTTP or HTTPS address. Read the specific validation message before saving.

Do not insert a made-up value just to pass validation. If a required field no longer fits the workflow, ask the administrator responsible for the schema. The mobile validation helps identify input errors; the server remains authoritative.

5. Review the whole edit and save once

1. Check contact details as well as ownership, assignment, company, sharing and custom fields.
2. Use Save changes and wait for its result.
3. Reopen the same contact and verify the saved values.
4. After an interrupted response, inspect the current record before retrying.

The editor submits a complete set of fields, so avoid leaving it open while someone else makes substantial changes. This guide does not promise a revision-conflict safeguard for every contact update. If another person edited the record, compare the latest values before submitting your changes again.

6. Verify the intended teammate’s access

Have the authorized teammate check the contact through their own normal account. Do not share your login to demonstrate access. Confirm the intended view and edit capabilities without granting unnecessary account permissions. If access differs from expectation, compare the saved sharing, ownership and role rather than repeatedly adding recipients.

Related guides

• Organize your contacts
• Organize companies and contact fields

Reviewed 13 October 2026 against the current IllyVoIP controls, implementation and applicable references. Available options depend on account permissions and service state.