Interactions may need to be deleted in an iService tenant. For example, in some cases sensitive data like credit card numbers must be removed for compliance reasons.  Or, your database might grow large and require you to purge interaction data to reduce its size.

 

iService contains a stored procedure to delete interactions, but it cannot be accessed from the web interface and must be run by a system  administrator or DBA with access to execute the iServiceInteractionsDelete stored procedure in the tenant database.

 

Notes:

•Deleting an Interaction is unrecoverable and removes all relational data connected to it, including:

oAudit trails of the interactions status and properties

oIf interaction was sourced from an email, all related raw email and post-processed email data

•Other interactions in the same thread are NOT deleted.  For example, if a customer emails in sensitive data and an agent replied to them with the original email quoted,  both the customer email AND the agent reply must be deleted seperately.

•If the parent of a child interaction is deleted, the child's grandparent interaction will be inherited as its parent, recursively.  If the parent of a child interaction was the thread root, the child interaction and its siblings will all become thread roots.

 

 The procedure simply takes one argument: the interaction ID

 

Example:

EXECUTE [dbo].[iServiceInteractionsDelete] 123456

 

iService includes a stored procedure to mass deleted interactions, but you must first construct a query to derive the list of interactions to purge. For assistance with performing a mass delete on your database please contact One-to-One Service.com at support@1to1service.com.