import { ActionBlockProps } from '../mappings/blocks';
/**
 * `contact_support_block` (`insights_v2.2.md` §7.3) is the help module's contact-support flow,
 * but insights-v2 must **not** import it: hosts that don't ship the Help widget (pulse's webpack
 * config `IgnorePlugin`s every `help` resource inside `@mx-cartographer/experiences/dist`) would
 * get a `webpackMissingModule` stub and crash at import time. So the flow is injected instead:
 *
 * - Feed / mini cards: the host passes `beatActions.onContactSupport` (pulse already threads
 *   `beatActions` into `BaseLayout`). `BaseLayout` calls it directly instead of opening a drawer.
 * - Transaction details drawer: the host passes `onContactSupport` to `TransactionDetails`.
 * - The experiences Help widget is itself a host and wires `RequestSupport` through the same hook.
 *
 * The CTA renders disabled (label shown, `aria-disabled`, nothing opens or posts) whenever the
 * client's `enable_support_requests` is off **or** the host supplied no handler — see
 * `isContactSupportCtaDisabled`.
 *
 * This registry entry is only a safety net for a drawer opened by a path that bypassed that gate
 * (e.g. a stale `actionDrawer` state): it hands off to the host handler if one exists, otherwise
 * closes the drawer and shows the generic error.
 */
export declare const ContactSupportActionBlock: ((_props: ActionBlockProps) => import("react/jsx-runtime").JSX.Element | null) & {
    displayName: string;
};
/**
 * Whether a host must render a CTA disabled. Only `contact_support_block` is gated: by the client's
 * `enable_support_requests` config (default false) and by whether the host actually wired a handler.
 * Every other block is always enabled. No fallback to a host post message when it is off.
 */
export declare const isContactSupportCtaDisabled: (block: string | null | undefined, config: {
    enable_support_requests?: boolean;
}, onContactSupport?: (() => void) | null) => boolean;