Use Client Preferences to inspect recognised SMS fields left by an earlier module and carry their answers into the PD Azure SMS preferences. Review what each field means before copying; a generic Accept SMS tick is not a substitute for a separate marketing choice.

Review the detected fields

Open PD Modules → Azure SMS → Client Preferences and look for Fields from another SMS module. The panel shows recognised fields, answers held, tick counts and advice. It detects supported field patterns rather than promising to import every custom arrangement.

Review the preference categories and wording you intend to offer. If a destination category is not switched on, the panel can report that its answers have nowhere to go yet. Decide the intended choices before applying an import; do not enable an unrelated category simply to clear a warning.

Carry the answers across

1. Read the field preview and the proposed action.
2. Choose Copy these answers across when it matches the intended migration.
3. Read the confirmation, then confirm the supported copy action.
4. Review the result and each field’s updated status.
5. Inspect a controlled test profile’s number and choices before normal automatic messaging.

The workflow retains original fields and avoids overwriting a newer answer a client already supplied. It can adopt an existing number field as the continuing phone-number source rather than moving its values into a duplicate field. Treat the result message as the description of what happened, not a promise that every number was copied elsewhere.

Keep fields still in use

In use means the module is still reading that number field: keep it. Finished is the panel’s summary status. Check the intended client answers and any other use of the field before considering removal; do not treat the summary alone as proof that every individual answer is present. Keeping the original field while reviewing is preferable to losing it. The import action itself deletes nothing.

A previous blanket refusal is applied across the offered categories. A previous general acceptance keeps the intended defaults without inventing a separate marketing agreement. Rechecking should preserve existing answers, but it is not a way to reverse a client’s later choice.

If a field is not recognised or the result is unclear, keep the original fields while your hosting team compares the preview, destination categories and controlled profile answers. Do not bulk-copy stored client values as a repair.

Several SMS modules on one installation

When several PD SMS modules are enabled, a single module manages the shared client-profile fields. PD SMS Manager takes precedence when present. Follow any Client Preferences message identifying that module and make shared profile-setting changes there. Check PD Azure SMS’s own category rules, phone source and gateway routing separately; a shared profile summary does not prove every enabled module’s sending configuration.

See the PD Azure SMS WHMCS guide for related tasks, or explore PD Azure SMS.