Without code, Beacon is configurable in look and layout: colors, wording, which of contact, Docs and chat appear, and where it sits on the page. Every visitor sees the same widget with the same suggested articles. That's fine for a marketing site, but on a logged-in app it means agents get conversations from "unknown" senders and customers retype details you already hold.
identify fixes the first part. Beyond name and email it takes company, job title, an avatar URL and custom properties (text up to 255 characters, numbers, URLs, dates as YYYY-MM-DD, or dropdowns that must match an option label exactly), plus company-level properties. Leave a property out and it stays as it was; send an empty string and it's removed from the customer. Your own site has to make that call with the right data, because Beacon doesn't look anything up by itself.
n-frames does that wiring for Help Scout customers: identify fed from your account system the moment a page loads, session data carrying the order or account the visitor is looking at, a signing endpoint for Secure Mode, and suggestions mapped route by route. For pulling Beacon conversations into other systems once they arrive, that's the Help Scout API, and the Help Scout overview covers the help desk itself.