{"section":"known-issues","requestedLocale":"en","requestedSlug":"telesales-impersonation-fails-for-specific-customers-in-unified-profile-system-stores","locale":"en","slug":"telesales-impersonation-fails-for-specific-customers-in-unified-profile-system-stores","path":"docs/en/known-issues/Store Framework/telesales-impersonation-fails-for-specific-customers-in-unified-profile-system-stores.md","branch":"main","content":"## Summary\n\nIn B2B telesales flows, impersonation via the telesales bar intermittently fails for some shopper emails: the session never assumes the customer context and profile.isAuthenticated stays false in the Session API. Operators can impersonate certain customers successfully (often those with previous orders), while others consistently fail.\n\n## Simulation\n\n- Store with telesales operators enabled.\n- Account that has undergone Profile System unification.\n- Using the telesales bar, attempt impersonation with a customer email and observe the session. Check the sessions API response, if the client is correctly set: profile.isAuthenticated:true and a profile.id are returned.\n- If failed, check the customer email and check the sessions API response. Observe that profile.isAuthenticated:false and no customer profile.id are returned.\n\n## Workaround\n\nAlways make sure the user is on the masterdata of the parent account, and has a active profile."}