WEBVTT

00:00:00.299 --> 00:00:03.072
Start with one scene that contains a clear conflict or

00:00:03.115 --> 00:00:03.755
charged image

00:00:04.395 --> 00:00:06.997
A specific moment gives HookHero more to work with than

00:00:07.040 --> 00:00:09.396
a vague description of the whole book In this prepared

00:00:09.694 --> 00:00:09.908
example

00:00:10.505 --> 00:00:12.894
the source is a fictional gothic archive scene

00:00:13.406 --> 00:00:15.881
We will follow the workflow from source material to a

00:00:15.924 --> 00:00:17.374
small set of hooks worth reviewing

00:00:17.971 --> 00:00:20.702
This is a guided screen reference not a live generation

00:00:20.873 --> 00:00:21.129
recording

00:00:21.830 --> 00:00:23.963
Open the full app through My Library with the access

00:00:24.219 --> 00:00:25.798
your purchase or membership includes

00:00:26.267 --> 00:00:28.230
HookHero Lite is a separate starting option

00:00:28.998 --> 00:00:29.766
For AI generation

00:00:30.321 --> 00:00:32.881
connect a supported provider and select an available model

00:00:33.510 --> 00:00:35.345
API usage is billed by that provider

00:00:35.900 --> 00:00:38.758
A chat subscription and an API balance are different things

00:00:39.228 --> 00:00:42.385
Never put an API key in your story text screenshots

00:00:42.726 --> 00:00:43.409
or shared notes

00:00:44.212 --> 00:00:44.894
Paste the scene

00:00:45.364 --> 00:00:48.521
premise chapter summary or other source you want to market

00:00:49.161 --> 00:00:51.550
You can also use the selected Book DNA for richer

00:00:51.636 --> 00:00:52.062
context

00:00:52.745 --> 00:00:54.409
Check the active book before generating

00:00:55.120 --> 00:00:57.979
The source should establish the tension and reader promise without

00:00:58.150 --> 00:00:59.472
requiring invented plot details

00:01:00.411 --> 00:01:01.478
If you have several pen names

00:01:02.032 --> 00:01:04.550
confirm the voice and book context belong to the one

00:01:04.593 --> 00:01:05.233
you are working on

00:01:05.807 --> 00:01:08.153
Choose the tone that fits the book and use Cast

00:01:08.281 --> 00:01:09.561
the Spell to request the batch

00:01:10.159 --> 00:01:12.207
Read the resulting short hooks beside the source

00:01:12.804 --> 00:01:13.657
In the prepared screen

00:01:14.127 --> 00:01:16.815
the output gives several ways into the same archive moment

00:01:17.442 --> 00:01:20.557
A useful hook creates curiosity while remaining faithful to the

00:01:20.600 --> 00:01:20.770
story

00:01:21.282 --> 00:01:24.397
Reject a striking line if it invents a relationship event

00:01:24.866 --> 00:01:26.146
or promise your book does not support

00:01:27.040 --> 00:01:30.112
Look at the Instagram openings and newsletter teasers as well

00:01:30.198 --> 00:01:30.795
as the short hooks

00:01:31.392 --> 00:01:32.118
Choose one idea

00:01:32.672 --> 00:01:34.465
then adapt its length and voice for the channel

00:01:35.019 --> 00:01:37.878
Add the real book title or destination where appropriate

00:01:38.432 --> 00:01:41.376
Do not post every generated option just because it exists

00:01:42.186 --> 00:01:44.960
Your next decision is which one best invites the right

00:01:45.088 --> 00:01:46.496
reader into this particular book

00:01:47.043 --> 00:01:50.030
Copy the individual result or download the batch as text

00:01:50.286 --> 00:01:51.609
so you can revise it outside the app

00:01:52.163 --> 00:01:54.040
Keep the source and the final version together

00:01:54.766 --> 00:01:55.363
Before posting

00:01:55.832 --> 00:01:56.344
check spelling

00:01:56.899 --> 00:02:00.142
book facts spoilers links and the call to action

00:02:00.794 --> 00:02:03.227
Test one clear variation and record the result

00:02:03.909 --> 00:02:04.976
If the post underperforms

00:02:05.488 --> 00:02:08.218
bring that actual post and its context into the Hook

00:02:08.304 --> 00:02:09.541
Graveyard for a focused review