Less searching. More moving forward.

Inbox setup connects outgoing and incoming mail. Provider lead intake is a separate integration using a source’s posting URL and key. To land a provider enquiry as a lead, follow the provider setup guide and verify its live acknowledgement.

Yes for a complete third-party inbox setup. Choose a provider preset to fill both sets of server settings, then enter your credentials once with reuse enabled. Save and test sending and receiving separately.

No, and nobody can — MegaHub stores a hash of the key rather than the key itself, so it cannot be read back out by support, an owner, or anyone with database access. Rotate it under Settings → Lead sources and send the vendor the new one. Arrange the swap with them first: the old key stops working the moment the new one is issued.

The response will not tell you, on purpose — an unknown tenant key and a wrong posting key return the identical 401 so the endpoint cannot be used to discover which keys are live. Check three things: the tenant key in the URL, the posting key in the X-Api-Key header, and whether that lead source is still switched on.

Almost always a field name mismatch — the provider is sending something like zipcode where MegaHub reads origin_zip. The post succeeds because unrecognised fields are ignored rather than rejected, so nobody notices until an agent opens the lead. Run the same payload against the test endpoint, which lists exactly which fields were ignored.

Check the server, port and security mode in Advanced server settings. SMTP presets use implicit TLS on 465, while iCloud uses STARTTLS on 587. IMAP presets use TLS on 993. Save your correction, then run the SMTP and IMAP tests separately. Saving alone does not verify the connection.

Usually one of two things. Either your domain is missing SPF, DKIM or DMARC records, or the From address is on a different domain from the mailbox you connected — a mismatch that receiving servers treat as a forgery. Both are fixed outside MegaHub, in your DNS and your mail provider.

Yes. Connect that agent’s mailbox under Inbox → Mailboxes and configure SMTP and IMAP. Each agent uses their own saved credentials, and the sending test confirms which address the message leaves from. A matching domain alone does not configure an agent’s mailbox.

Suspend the user rather than deleting them, then have a manager or admin reassign their open work. Suspending locks them out immediately, including any session already open, while leaving their history attached to a real name. Suspended users are not counted in your bill.

No — it exports every record you are allowed to see, ignoring the filters and column searches on the page. A spreadsheet exists to do the analysis the table cannot, and an export shaped by whatever chips happened to be set is a report that silently omits rows.

Duplicate the quote rather than raising a second lead. The copy asks for the new ship date and stays on the same lead, so the customer's enquiry remains one record with two offers against it. The original is untouched.

Yes. Adding a vehicle adds it to that quote and re-totals the header — you do not need to re-quote the lead. The per-vehicle prices and the header totals are the same figures read two ways, so editing either keeps both correct.

You are almost certainly signing the re-serialised body rather than the raw one. Parsing and re-encoding JSON changes key order and whitespace, so the bytes differ from what was signed. Capture the body exactly as it arrived, before any parser touches it, and HMAC over the timestamp, a full stop, then those raw bytes.

One per request, until you enable batch posting for that specific key and set a limit. The hard ceiling is 200 per request, and you can also cap a vendor by the hour. Both are set per posting key, so a new vendor cannot flood the board before you have seen what they send.

Because the processor's own card form is not connected yet. The storage behind it is finished and encrypted, and nothing you have configured under Payments is wasted — this is the last piece. Take the payment through your processor's portal in the meantime.

Each method has its own Available to team leads switch, and it is off until an admin turns it on. Admins can always use every enabled method, which is why it looks fine from an admin account. Turn it on under Settings → System settings → Payments.

No. A dispatch sheet describes a specific set of vehicles, and taking some away would leave a driver holding paper for a load that no longer exists in that shape. Split the order first, then dispatch each part to its own carrier.

The board refused it, and MegaHub left the order unlisted rather than pretending it had gone up. Use Post to board on the order — it repeats the board's own reason, which is usually something like a ready date in the past or a missing ZIP. Pressing it on an order that is already listed is safe and will not create a duplicate advert.

Yes. Suspended users are not billed, and the change takes effect immediately. Invited users who have not signed in yet are billed, because the seat is claimed the moment the invitation goes out.

That is the default, and it is the point of having teams. If a manager genuinely needs brokerage-wide sight, grant them leads.view_all — the permission matrix is editable under Settings → Roles, so it is a settings change rather than a support ticket.

No. A token is issued by the gateway that created it and cannot be charged anywhere else, so saved cards stop being chargeable and have to be re-entered. Some processors will migrate tokens for you — ask them before you switch, not after.